Reword Okta SCIM notes and add new requirement
What does this MR do and why?
Describe in detail what your merge request does and why.
-
I have reorganized the things to do into a list for before starting configuration for Okta SCIM. This should make it easier for users to go through as a checklist.
-
I have added a new item to the list
(pending confirmation from Support, or someone in Okta). About GitLab Okta SCIM requiring provisioners use the Okta's Lifecycle Management product in order to proceed. This came up from a customer who shared that they were not able to follow through the SCIM instructions on their Okta setup (internal ZD ticket), after having set up SAML SSO, and it turns out that they do not have the Okta feature to provision SCIM. -
Got confirmation from our colleague @Mwhitaker who used to work at Okta that the LCM tier is required for SCIM provisioning:
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
In my own Okta test instance, and following through our Okta SCIM notes, the GitLab Okta SCIM app is found in the app catalogue which has a Use Case category for "Lifecyle Management".
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Refer to step 3 of Okta configuration steps: "In the Application tab, select Browse App Catalog."
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.