docs: Document supported SCIM features and correct the deprovisioning and base URL guidance - #8221
Conversation
… base URL guidance Adds a supported-features section and the three user attributes we actually read, both asked for by the Okta OIN reviewers. Also corrects three things the docs got wrong: deprovisioning works through DELETE only (support for the `active` attribute was removed), the SCIM base URL must not have a trailing slash, and the Okta section now says where the base URL and token come from. beep boop
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
📝 WalkthroughWalkthroughThe SCIM documentation lists supported and unsupported features, supported user attributes, and DELETE-only deprovisioning. It updates SCIM URL and token setup guidance. The Okta guide adds configuration steps and documents unassignment-based deprovisioning. Troubleshooting now covers exact URL matching and the 501 response for Estimated code review effort: 2 (Simple) | ~10 minutes Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The Okta section described the generic custom SCIM app flow: entering a SCIM connector base URL, a unique identifier field, supported provisioning actions and an HTTP Header auth mode. The Flagsmith OIN application has none of those fields. It derives the SCIM base URL from the API Base URL set under Advanced Sign-on Settings, and takes the bearer token as "API Token" under Provisioning > Integration. This matters because the submission's setup instructions link points at this anchor, so Okta's reviewers follow these steps. beep boop
There was a problem hiding this comment.
Looking good to me. Approving (to help unblocking) without knowledge of the exact requirements but I guessed improvements where about:
- activate versus delete
- trailing slashes ?
- user attributes mapping
- clear supported features
Which are clearly understandable from my pov
The `apibaseUrl` tenant variable has no default in the OIN submission, and it also feeds the SAML ACS URL template, so every customer sets it. beep boop
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 84737384-9612-4d51-a887-28ccc91aa5cb
📒 Files selected for processing (1)
docs/docs/administration-and-security/access-control/scim.md
4 participants
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
In this PR, we address feedback from Okta OIN team:
How did you test this code?
Docs-only change