Skip to content

Conversation

@grantmiller
Copy link
Member

No description provided.

@grantmiller grantmiller requested a review from a team as a code owner August 19, 2025 13:50
@netlify
Copy link

netlify bot commented Aug 19, 2025

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 4e4d586
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs/deploys/68a503ea8e04ff0008433b20
😎 Deploy Preview https://deploy-preview-3461--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Aug 19, 2025

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 4e4d586
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs-upgrade/deploys/68a503ea90e81c0008be93b7
😎 Deploy Preview https://deploy-preview-3461--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels Aug 19, 2025
* 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@grantmiller I'm not sure that I totally understood the flow here.

It sounds like:

  1. Meet the requirements (ie, enable SAML etc)
  2. Do the idp configuration (in this case, we show Okta steps)
  3. Migrate users using the automated or manual steps (this is only necessary if you already have users in your replicated team)
  4. Test the integration

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's correct

```
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it could be moved... we probably just need to document okta

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor

@paigecalvert paigecalvert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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

@paigecalvert
Copy link
Contributor

merging!

@paigecalvert paigecalvert merged commit e7fc92c into main Aug 20, 2025
5 checks passed
@paigecalvert paigecalvert deleted the scim-draft branch August 20, 2025 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants