Closed Bug 1209530 Opened 10 years ago Closed 10 years ago

add-on content tools login button doesn't go to fxa login

Categories

(Marketplace Graveyard :: Developer Pages, defect, P4)

Avenir
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: eviljeff, Assigned: kngo)

References

Details

The Login button always goes to the register page instead of the login page.
Priority: -- → P4
Blocks: 1195470
Is this still an issue? it works fine for me
Yes. Make sure your account is cleared first (i.e. click on "Use a different account")
https://github.com/mozilla/marketplace-content-tools/pull/64 Removing the Register button entirely since it doesn't do anything differently from the Login button. This issue may still exist, but it's all FXA logic that we have no control over.
STR: Expected: Register buttons removed. FXA will still take you to the register page if it doesn't detect a previous session.
Assignee: nobody → kngo
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
If fireplace can do it, why can't content-tools do it? In the consumer pages, Register goes to `/oauth/signup`; Login goes to `/oauth/signin`. For content tools they both seem to go to /oauth and fxa redirects.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Ah, must be because we're using fxa-dev on -dev.
It should work on stage once we get to that point then.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → WONTFIX
Hey Kevin, could you clarify the fxa-dev comment? We'd like to run automated tests on both dev and staging so would like to have these flows being consistent. FYI, we also saw this on fireplace and raised bug 1162010.
Status: RESOLVED → REOPENED
Flags: needinfo?(kngo)
Resolution: WONTFIX → ---
See Also: → 1162010
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Flags: needinfo?(kngo)
Resolution: --- → FIXED
Thanks for this fix, Kevin. This makes it much easier to write an automated test.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.