Closed
Bug 700751
Opened 13 years ago
Closed 13 years ago
support browser id
Categories
(Mozilla QA Graveyard :: MozTrap, enhancement)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: camd, Unassigned)
Details
we should support browser ID in Case Conductor
| Reporter | ||
Comment 1•13 years ago
|
||
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/20749707
| Reporter | ||
Comment 2•13 years ago
|
||
Carl Meyer added a comment in Pivotal Tracker:
This might be useful when we get here: http://blargon7.com/2012/02/automating-browserid-with-selenium/
| Reporter | ||
Comment 3•13 years ago
|
||
Cameron Dawson added a comment in Pivotal Tracker:
I'll take a crack at adding this functionality while Carl is busy on other things.
| Reporter | ||
Comment 4•13 years ago
|
||
Cameron Dawson changed story state to started in Pivotal Tracker
| Reporter | ||
Comment 5•13 years ago
|
||
Cameron Dawson added a comment in Pivotal Tracker:
Whew! I'm in over my head on this one. I started the branch and got some stuff put in. But Carl the hard stuff remains.
| Reporter | ||
Comment 6•13 years ago
|
||
Cameron Dawson added a comment in Pivotal Tracker:
docs for django-browserid: http://django-browserid.readthedocs.org/en/latest/setup.html
| Reporter | ||
Comment 7•13 years ago
|
||
Cameron Dawson added a comment in Pivotal Tracker:
brief presentation about django-browserid: http://htmlpad.org/django-browserid-preso-mar-2/#
| Reporter | ||
Comment 8•13 years ago
|
||
Carl Meyer added a comment in Pivotal Tracker:
Whoops. I spaced out and merged this branch into master before it was really done; shouldn't be a big problem, though, just odd placement of the BrowserID link on the login page until Eric gets to it. Not going to bother undoing the merge, Eric can just finish it up in master. It works, anyway!
| Reporter | ||
Comment 9•13 years ago
|
||
Cameron Dawson added a comment in Pivotal Tracker:
wahoo!!! \o/ Thanks Carl!!!
| Reporter | ||
Comment 10•13 years ago
|
||
Carl Meyer added a comment in Pivotal Tracker:
:-)
To test this locally, you need to make sure you have a SITE_URL setting that is the same URL by which you are accessing the TCM. The default value is "http://localhost:8000", but if you're like me and you use something like moz.hexxie.com locally, you'll need to add "SITE_URL = 'http://moz.hexxie.com:8000'" to your settings/local.py.
Cam, I've created a task for you to make sure solarce adds that SITE_URL setting to both allizom sites, otherwise BrowserID login won't work.
Eric, for your first task here, we somehow need to communicate to users that there are two options for logging in; either BrowserID (for which you click a link), or the login form. I'll leave it up to you how best to do that - Cam, maybe you can clarify which option should be more "featured"? Feel free to move the link around in the source (in users/login.html); just keep it together with the form right below it. You might consider using one of the "standard" BrowserID login icons from https://developer.mozilla.org/en/BrowserID/Quick_Setup
For the second task, I just noticed again that user messages on the login page have an odd large left indent. You can see an error message by trying to BrowserID-login using an email address that has no account.
| Reporter | ||
Comment 11•13 years ago
|
||
Cameron Dawson added a comment in Pivotal Tracker:
carl/eric: I think browserid should be more featured.
| Reporter | ||
Comment 12•13 years ago
|
||
Cameron Dawson added a comment in Pivotal Tracker:
OK, I entered an IT ticket to update the local.py: https://bugzilla.mozilla.org/show_bug.cgi?id=740031
| Reporter | ||
Comment 13•13 years ago
|
||
Cameron Dawson added a comment in Pivotal Tracker:
looks like this is working on -dev. It's just up to you, Eric, to make it pretty! :)
| Reporter | ||
Comment 14•13 years ago
|
||
Eric Meyer changed story state to delivered in Pivotal Tracker
| Reporter | ||
Comment 15•13 years ago
|
||
Cameron Dawson changed story state to accepted in Pivotal Tracker
| Reporter | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•