Closed
Bug 912481
Opened 12 years ago
Closed 12 years ago
Persona login is not using LDAP bridge
Categories
(Marketplace Graveyard :: Integration, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: eviljeff, Unassigned)
References
Details
If I try to login to Marketplace (on either Destkop, Android or FxOS) the login for my @mozilla.com email address is not using mozilla LDAP authentification, but is instead falling back on the old password I had previously.
Logging in to a private etherpad (not on the same profile) correctly uses LDAP during the persona login sequence.
Comment 1•12 years ago
|
||
A few days ago, we totally were. This was regressed with this commit, which went out yesterday:
https://github.com/mozilla/fireplace/commit/cb53c2f#L0R66
Kumar, evidently setting an unverified issuer disallows us from using the Mozilla LDAP authentication. I don't know enough about Persona to know whether that's expected behaviour - but yeah that's what's happening here.
Keywords: regression
| Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(kumar.mcmillan)
Comment 2•12 years ago
|
||
This is not a regression. We removed the primary bridging capabilities because it is not possible for Firefox Marketplace to support it. Why not? Because we *also* support unverified accounts so that the user can unbox a phone and make a payment. We had to disable primaries because of this potential exploit: bug 910938
What this means for users is that they will always log in with the same username and password on both desktop and Firefox OS. As of 9/3, on desktop, users may be prompted to create a username/password if they have never used Firefox OS before.
Before we fixed this, certain users were locked out of Firefox OS entirely because their login did not work. See https://github.com/mozilla/browserid/issues/3842
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(kumar.mcmillan)
Keywords: regression
Resolution: --- → WORKSFORME
Comment 3•12 years ago
|
||
TLDR; as long as we support allowUnverified=true in at least one place we have to use forceIssuer *in all places*
You need to log in
before you can comment on or make changes to this bug.
Description
•