Actions
Bug #15867
closed
LoginCluster redirect broken with EnableBetaController: true
Story points:
-
Release:
Release relationship:
Auto
Description
So this note was precient https://dev.arvados.org/issues/15107#note-27
The login redirect generated by Controller passes an empty "remote" which causes the target cluster to fail:
https://172.17.0.2:8000/login?remote=&return_to=https%3A%2F%2F172.17.0.3%2Fusers%2Fwelcome%3Freturn_to%3D%252F
{"errors":["Invalid remote cluster id (req-1dbjeioi2ubya1rjphw3)"],"error_token":"1574438263+155fa05c"}
Either controller shouldn't do that, or the API server should accept that (or both).
Related issues
Updated by Peter Amstutz almost 5 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz almost 5 years ago
- Status changed from In Progress to New
Updated by Peter Amstutz almost 5 years ago
- Description updated (diff)
- Assigned To set to Tom Clegg
Updated by Peter Amstutz almost 5 years ago
- Related to Task #15512: Review 15107-google-login added
Updated by Peter Amstutz almost 5 years ago
- Related to deleted (Task #15512: Review 15107-google-login)
Updated by Peter Amstutz almost 5 years ago
- Related to Idea #15107: [controller] Implement native Google login (configurable as an alternative to sso-provider) added
Updated by Tom Clegg almost 5 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|1b6b00b1f3f1a1931c27c69f1624d2c34e94a880.
Actions