Conversation
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
replicated-ci
added
type::docs
| * You have a Vendor Service Account token with permissions to manage team members. See [Generate API Tokens](/vendor/replicated-api-tokens). | ||
| * You have administrative access to your identity provider. | ||
|
|
||
| ## Configure SCIM |
There was a problem hiding this comment.
@grantmiller I'm not sure that I totally understood the flow here.
It sounds like:
- Meet the requirements (ie, enable SAML etc)
- Do the idp configuration (in this case, we show Okta steps)
- Migrate users using the automated or manual steps (this is only necessary if you already have users in your replicated team)
- Test the integration
| ``` | ||
| Where `YOUR_TOKEN` is a Replicated Vendor Service Account token scoped to your team with permissions to manage team members. For more information, see [Authentication](#authentication) below. | ||
|
|
||
| ### Generic SCIM Provider Configuration |
There was a problem hiding this comment.
I'm not certain about the purpose of this "Generic SCIM Provider Configuration" section.
It looks like it duplicates some of the info already doc'd under the SCIM API section.
Is there a specific call-to-action here, or could this info be moved under the SCIM API section?
There was a problem hiding this comment.
it could be moved... we probably just need to document okta
There was a problem hiding this comment.
gotcha. so it's meant to be info for people if they don't use okta. I'll do one more pass and see about cutting down on this content
paigecalvert
left a comment
paigecalvert
left a comment
There was a problem hiding this comment.
@grantmiller made a few updates and approving whenever you are ready to merge. I think these are good for beta docs, and then we can improve them as needed
|
merging! |
3 participants
No description provided.