If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Authentication process no longer returns a valid etherpad url

RESOLVED WORKSFORME

Status

Infrastructure & Operations
WebOps: IT-Managed Tools
RESOLVED WORKSFORME
4 years ago
3 years ago

People

(Reporter: hwine, Unassigned)

Tracking

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/229] )

(Reporter)

Description

4 years ago
After authenticating to an etherpad, I am no longer returned to the pad I signed into. Instead, I get an empty page with a URL similar to the following:
  https://infra.etherpad.mozilla.org/ep/account/sign-in?cont=https%3a%2f%2finfra.etherpad.mozilla.org%2fEngOps

I've received this on both persona (above) and password protected pads. I've only seen it on "team pads" such as infra.e.m.o & releng.e.m.o

I first started seeing this approx Aug 8 -- if it doesn't match to any changes in etherpad, then it's due to upgrade to FF 23 (release). Seems unlikely that we'd have missed that with internal beta testing, so filing here first.
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/118]

Updated

3 years ago
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/118] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2482] [kanban:https://kanbanize.com/ctrl_board/4/118]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2482] [kanban:https://kanbanize.com/ctrl_board/4/118] → [kanban:https://kanbanize.com/ctrl_board/4/118]

Updated

3 years ago
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/118] → [kanban:https://webops.kanbanize.com/ctrl_board/2/229]
I'm not sure what changed, but I tested the above sign-in URL today on a fresh browser instance and it worked perfectly, asked my LDAP and signed me in and took me to the page. So I'm going to resolve this as WORKSFORME.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.