Closed Bug 1020020 Opened 10 years ago Closed 10 years ago

Primary identity provisioning is broken on b2g

Categories

(Core Graveyard :: Identity, defect)

Other Branch
All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
2.1 S2 (15aug)

People

(Reporter: jedp, Assigned: edwong)

Details

STR:

In b2g, 

- Open UI Tests -> API -> Persona mozId
- Click Request
- Try to sign in with a primary identity (e.g., mozilla.com address)

Observed:

Provisioning hangs with these errors in console:

E/GeckoConsole(17036): [JavaScript Warning: "The X-Content-Security-Policy and X-Content-Security-Report-Only headers will be deprecated in the future. Please use the Content-Security-Policy and Content-Security-Report-Only headers with CSP spec compliant syntax instead." {file: "https://login.mozilla.org/provision" line: 0}]
I/Gecko   (17036): nsDOMIdentity ({1f4b18d7-231f-47e5-8771-33398706c6c3}): init was called from https://login.mozilla.org/provision
E/GeckoConsole(17036): [JavaScript Warning: "SyntaxError: Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead" {file: "https://login.mozilla.org/js/lib/jquery.min.js" line: 1}]
E/GeckoConsole(17036): [JavaScript Warning: "Error: https://login.mozilla.org/js/lib/jquery.min.js is being assigned a //# sourceMappingURL, but already has one"]
I/Gecko   (17036): nsDOMIdentity ({1f4b18d7-231f-47e5-8771-33398706c6c3}): beginProvisioning
I/Gecko   (17036): nsDOMIdentity ({1f4b18d7-231f-47e5-8771-33398706c6c3}): DOMIdentityMessage: {"errors":[],"id":"{1f4b18d7-231f-47e5-8771-33398706c6c3}","origin":"https://login.mozilla.org","appStatus":0,"audience":"https://login.mozilla.org"}
E/GeckoConsole(16573): [JavaScript Error: "getService called before newContext for {1f4b18d7-231f-47e5-8771-33398706c6c3}" {file: "resource://gre/modules/DOMIdentity.jsm" line: 201}]
E/GeckoConsole(17036): [JavaScript Warning: "Content Security Policy: The page's settings blocked the loading of a resource: An attempt to execute inline scripts has been blocked" {file: "https://login.mozilla.org/provision" line: 0 column: 0 source: "onsubmit attribute on DIV element"}]
E/GeckoConsole(17036): [JavaScript Warning: "Content Security Policy: The page's settings blocked the loading of a resource: An attempt to execute inline scripts has been blocked" {file: "https://login.mozilla.org/provision" line: 0 column: 0 source: "onchange attribute on DIV element"}]
E/GeckoConsole(17036): [JavaScript Warning: "Content Security Policy: The page's settings blocked the loading of a resource: An attempt to execute inline scripts has been blocked" {file: "https://login.mozilla.org/provision" line: 0 column: 0 source: "onsubmit attribute on DIV element"}]
E/GeckoConsole(17036): [JavaScript Warning: "Content Security Policy: The page's settings blocked the loading of a resource: An attempt to execute inline scripts has been blocked" {file: "https://login.mozilla.org/provision" line: 0 column: 0 source: "onchange attribute on DIV element"}]


Corresponding github issue filed for Persona: https://github.com/mozilla/persona/issues/4144
Other primaries include gmail.com, yahoo.com email addresses. Also, any dummy user at mockmyid.com could be used without needing a password.
(In reply to Jared Hirsch [:_6a68] [@6a68] from comment #1)
> Also, any dummy user at mockmyid.com could be used without needing a password.

This sounds like the RP is using forceIssuer, like the Marketplace.

Can someone that's seeing this bug:

1. Attempt to log into 123done.org using something @mockmyid.com?
2. Attempt to log into 123done.org using something @gmail.com?

Do those work?
I've tried signing into 123done.org using a mozilla.com address (which is a valid primary) using a FirefoxOS 1.1 build for Unagi from last October (2013-10-09).  Same problem. [1]

That would suggest that the problem is server-side to me (which would be nice; much easier to fix :)

[1] See https://github.com/mozilla/persona/issues/4144#issuecomment-45240587
Ditto Comment 3 for a mockmyid.com address
this is fixed as of Aug 4 - https://github.com/mozilla/identity-ops/issues/168
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee: nobody → edwong
Target Milestone: --- → 2.1 S2 (15aug)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.