Closed Bug 711625 Opened 13 years ago Closed 13 years ago

stale sessions cause 500 with BrowserID login

Categories

(Participation Infrastructure :: Phonebook, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: ozten, Assigned: ozten)

Details

Stale sessions cause 500 with BrowserID login ISE with OTHER: {'info': 'SASL(-1): generic failure: ', 'desc': 'Other (e.g., implementation specific) error'}
We should detect stale assertions and prompt the user to login.
Assignee: nobody → ozten.bugs
Target Milestone: --- → 2.1
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
In order to test this, we'll need to have sessions timeout. This can be done manually or we can shorten the cron that clears the session db current. I have access to the database to clear out sessions manually, ping me in IRC.
Target Milestone: 2.1 → 1.2
Verified stale session prompts user to sign in- goes to home page, rather than giving an error.
Status: RESOLVED → VERIFIED
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Target Milestone: 1.2 → ---
Version: unspecified → other
You need to log in before you can comment on or make changes to this bug.