Closed
Bug 594568
Opened 15 years ago
Closed 15 years ago
Authenticate directly on AMO database
Categories
(Mozilla Labs Graveyard :: FlightDeck, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
1.0
People
(Reporter: zalun, Assigned: zalun)
Details
Use given credentials to authenticate users using direct access to AMO db.
Updated•15 years ago
|
Assignee: nobody → zaloon
| Assignee | ||
Comment 1•15 years ago
|
||
http://github.com/zalun/FlightDeck/commit/2c62073128b380bfa4e2e3329863350a76f1ff00
SignIn form is now responding with the error code if 500 Error
FlightDeck checks if the settings for authentication database
are provided (in flightdeck/settings_local.py, commented out
example in flightdeck/settings_local-default.py)
Then it tries to authenticate against database.
In case of exception or no auth_database info authentication will scrape AMO
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 2•15 years ago
|
||
Thanks for linking the commit. I added some comments
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 3•15 years ago
|
||
http://github.com/zalun/FlightDeck/commit/32a10b65111a505df5531dd9e9860a0360ac9275
This is removing the AMO scraping
Still working on logging - I will file another bug for that thought
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Target Milestone: -- → 1.0
You need to log in
before you can comment on or make changes to this bug.
Description
•