Closed Bug 1016602 Opened 11 years ago Closed 11 years ago

Non-admin users getting logged out when adding an event

Categories

(Webmaker Graveyard :: Events, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cassie, Assigned: cade)

Details

(Whiteboard: [events-mp][may30])

Amira has gotten several emails today about folks getting logged out when they try to add an event. amirad: Here's a description from someone on albania this morning "I tried to add an event on the Webmaker event list, but Persona logs me out automatically after some seconds. Wierd…" Most people are having the exact same problem - this is the complaint for 3 of them "The website for signing up an event is super broke from my end. Have you had any complaints? If I click anywhere off the page, it reloads and says I'm not logged in." Cade looked into it a bit and found: cade: woah cade: the app just logged me out cade: lol "X-CSRF-Token: undefined" might be troublesome cade: okay, so when I manage to get around login issues, I'm definitely seeing an internal server error on event creation (for non admin accounts) I was able to add an event, presumably b/c I am an admin?, although it didn't show up in Upcoming events. Filed another bug for that – bug 1016572
Assignee: nobody → cade
Status: NEW → ASSIGNED
* Chris can you do a quick update on this one when you have a sec? Want to make sure we communicate well with users affected by this.
Flags: needinfo?(cade)
This was being caused by a bad config on the production events app. It wasn't properly setting the super cookie for webmaker logins. I've updated the config, and everything appears to be okay. Lets leave this open for a bit and confir that things are working again.
Flags: needinfo?(cade)
* Thanks for solving this Chris. * Any updates?
I asked the people who had the issue to re-upload and it seemed to work fine (for those that actually re-uploaded).
It sounds like we can officially call this resolved!
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.