Keep SAML Identity when deprovisioning via SCIM
What does this MR do and why?
- Currently on SCIM deprovision we remove the user's SAML identity and set the SCIM identity to active: false. But this means that if a user is reprovisioned they have no SAML identity and they cannot sign in. For enterprise users without a local GitLab database password lose access to their account and it cannot be reprovisioned/associated properly.
- This is behind a feature flag so that we can quickly roll it back if there is a problem.
- #379149 (closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
- Enable the
- Set up SCIM
- Set up SAML
- SCIM deprovision a user
- User's SAML Identity should still be in the database
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Jessie Young