Skip to content
This repository has been archived by the owner on May 10, 2019. It is now read-only.

[dev] signin with primary email address not working in dev #2624

Closed
jrgm opened this issue Oct 21, 2012 · 5 comments
Closed

[dev] signin with primary email address not working in dev #2624

jrgm opened this issue Oct 21, 2012 · 5 comments

Comments

@jrgm
Copy link
Contributor

jrgm commented Oct 21, 2012

STR

  1. Load http://dev.123done.org and click signin.
  2. In the dialog, enter an @eyedee.me email address.
  3. When prompted, click 'sign in with eyedee.me'.
  4. On eyedee.me, enter a password and click 'Sign in'.

The dialog returns to /sign_in#AUTH_RETURN, but doesn't complete signin.
Eventually, the error screen is shown with 'Action: Checking Email Address'.

This is working fine in stage and prod.

@ozten
Copy link
Contributor

ozten commented Oct 23, 2012

I can reproduce, following the STR.

https://eyedee.me/api/whoami

{"user":"ozten"}

I don't see the next expected call, a POST to eyedee.me/api/cert_key

Interestingly, no repro if I log into eyedee.me directly first.

Unable to troubleshoot with Chrome/Safari Dev Tools, getting "Uncaught TypeError: Cannot read property 'd' of undefined " dialog.js line 3.

@ozten
Copy link
Contributor

ozten commented Oct 23, 2012

Eyedee.me always uses the SHIM from https://browserid.org. Is this a valid test case? Maybe this isn't failing as soon as it did before?

@ghost ghost assigned lloyd Oct 23, 2012
@lloyd
Copy link
Contributor

lloyd commented Oct 23, 2012

taking

@lloyd
Copy link
Contributor

lloyd commented Oct 23, 2012

NOTE: @ozten 's comment about "cannot read property 'd' of undefined" was a separate five star, issue #2629, now fixed in dev.

Thinking the easiest way to move forward on this one is to bisect and isolate the commit where the breakage was introduced.

@lloyd
Copy link
Contributor

lloyd commented Oct 23, 2012

from deep in the bowels...

error: "runtime_error"
id: 264228
message: "{"message":"generator isn't seeded"}"

This may mean that the codepath used in #AUTH_RETURN is not seeding the random number generator. This may be related to load time optimizations, as I believe that the session_context call seeds said generator...

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

No branches or pull requests

4 participants