-
Notifications
You must be signed in to change notification settings - Fork 333
SQSERVICES-1519 IdP for SAML that was overridden by update cannot be added again #2400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
02ed7e0
96a5350
1caf1f5
f7b5d9a
e92473f
70a664c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| An IdP for SAML that was overridden can be added again | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -683,6 +683,7 @@ idpUpdateXML :: | |
| idpUpdateXML zusr raw idpmeta idpid = withDebugLog "idpUpdate" (Just . show . (^. SAML.idpId)) $ do | ||
| (teamid, idp) <- validateIdPUpdate zusr idpmeta idpid | ||
| GalleyAccess.assertSSOEnabled teamid | ||
| forM_ (idp ^. SAML.idpExtraInfo . wiOldIssuers) IdPConfigStore.deleteIssuer | ||
| IdPRawMetadataStore.store (idp ^. SAML.idpId) raw | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. if spar crashes at the right moment, this will cause the old idp to be deleted and the new not to be introduced, which is not fixable over the rest api (let alone the UI). I don't see a good way around this, though. It would be really nice to have transactions and postgres and everything. but i would like to have the comment below reflect this. (could you maybe also fix my typo there while you're at it ("epected")?)
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I moved the deletion to the end which leaves a less inconsistent state, in the case of a failure. And I added a comment. |
||
| -- (if raw metadata is stored and then spar goes out, raw metadata won't match the | ||
| -- structured idp config. since this will lead to a 5xx response, the client is epected to | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.