Documentation for self-managed SCIM setup
What does this MR do and why?
Describe in detail what your merge request does and why.
Documentation for SCIM for self-managed instances. Related to !106340 (merged) and epic &8902
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
Numbered steps to set up and validate the change are strongly suggested.
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.
Merge request reports
Activity
assigned to @dblessing
- Resolved by Adil Farrukh
@jglassman1 The docs at https://docs.gitlab.com/ee/user/group/saml_sso/scim_setup.html go further to describe setting up SCIM on the identity providers. It doesn't seem like a great idea to duplicate all of that. Do you think these docs are sufficient for now? Or should we move the identity provider pieces to a centralized location?
- Resolved by 🤖 GitLab Bot 🤖
Proper labels assigned to this merge request. Please ignore me.
@dblessing - please see the following guidance and update this merge request. 1 Error Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
- Resolved by Drew Blessing
- Resolved by Adil Farrukh
- Resolved by Drew Blessing
- Resolved by Jon Glassman
- A deleted user
added documentation label
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/user/admin_area/settings/scim_setup.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger -
requested review from @jglassman1
added devopsmanage sectiondev labels
added maintenancerefactor label
added typemaintenance label
@dblessing thanks for getting out the draft docs so quickly. I think we can use this as an MVC for 15.8, and iterate to add to the docs during subsequent milestones. I've also left some small suggestions.
- Resolved by Drew Blessing