Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Login Failing #6

Open
jswrenn opened this issue Sep 9, 2018 · 2 comments
Open

Login Failing #6

jswrenn opened this issue Sep 9, 2018 · 2 comments

Comments

@jswrenn
Copy link
Member

jswrenn commented Sep 9, 2018

When I try to sign on with my @brown.edu account, the request to http://examplar.cs.brown.edu/getAccessToken fails with error code 404. This only occurs with my @brown.edu account (which I've been using during the development process); I can login fine with other accounts. The problem persists across computers. I also seem to be the only user affected by this, as of now.

I seem to be getting stuck in this branch:

examplar/src/server.js

Lines 245 to 248 in eb59d73

if(u === null) {
noAuth();
return null;
}

@jpolitz do you have any idea what's going on here?

@jpolitz
Copy link
Member

jpolitz commented Sep 9, 2018

That should happen when the cookie coming from the browser doesn't represent a user that's stored in the database; that is, no key for the user id that maps to a refresh token.

One thing to check is if somehow a null token is in the database for the user id. I haven't seen that happen in CPO, but it's conceivably another way for null to show up here. Especially since it's a single account, maybe there's something with Brown or your account settings making the connection not work.

There's a script called src/scripts/dump-keys.js; you could lightly modify that and probably get the values printed out for keys, and figure out which one is for your failing user id, and see if it's a weird value (or if it's set at all).

Can you reproduce this on localhost, or just with the deployed examplar?

@jswrenn
Copy link
Member Author

jswrenn commented Sep 10, 2018

(Un?)fortunately, the problem seems to have spontaneously resolved itself today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants