Docs: Update SCIM enrollment for OIN - #69415
Conversation
kopiczko
added
backport-required
no-changelog
|
Amplify deployment status
Preview links for changed docs pages
|
There was a problem hiding this comment.
We're discouraging adding new images to the gravitational/teleport repo to cut down on repo size (we're working on an alternative image hosting/management workflow). Since this image consists mostly of text, would it make sense to describe the field names in text as well and remove the image?
There was a problem hiding this comment.
I'd prefer to stick with the image. It's 1:1 replacement, just with the updated UI.
There was a problem hiding this comment.
CC @zmb3 to make sure this is okay, since I know we've talked about images and repo size in the past.
| 2. Click 3-dots on the top-right corner of the **SCIM** tile and select **Enable**. | ||
|
|
||
| </details> | ||
| Note that saving new SCIM configuration will invalidate the existing SCIM token. |
| </details> | ||
|
|
||
| 2. Configure the SCIM integration with the generated token by clicking **Save SCIM Configuration** (it can be regenerated by refreshing the page and clicking the button again). | ||
| Save and copy the generated **Bearer Token** and store it for later. It will be required for the Okta Teleport app configuration. If **Save SCIM Configuration** button is not greyed out the token is not saved yet and it won't be working. |
There was a problem hiding this comment.
- "Save SCIM Configuration button" needs an article
- I would either make "it won't be working" more precise or remove it and leave this as "...the token is not saved yet."
|
@ptgott PTALA |
| </details> | ||
|
|
||
| 2. Configure the SCIM integration with the generated token by clicking **Save SCIM Configuration** (it can be regenerated by refreshing the page and clicking the button again). | ||
| Save and copy the generated **Bearer Token** and store it for later. It will be required for the Okta Teleport app configuration. If the **Save SCIM Configuration** button is not greyed out the token is not saved yet. |
There was a problem hiding this comment.
nit: "Save and copy...store it". It could be clear while working on the Okta UI but it reads a bit off here.
suggestion: Make these a separate sentence for clarity.
Rough example: Save the current settings by clicking X. A new SCIM bearer token will appear in the UI. Copy the bearer token and save it in a file as it will be required to configure Okta Teleport app.
There was a problem hiding this comment.
That's a good feedback. I tried to address both comments here: ac3ef2a
| </details> | ||
|
|
||
| 2. Configure the SCIM integration with the generated token by clicking **Save SCIM Configuration** (it can be regenerated by refreshing the page and clicking the button again). | ||
| Save and copy the generated **Bearer Token** and store it for later. It will be required for the Okta Teleport app configuration. If the **Save SCIM Configuration** button is not greyed out the token is not saved yet. |
There was a problem hiding this comment.
re: "button is not greyed out"
I would shy away from mentioning button colours tbh. Button action feedback UI can change anytime and this will be obsolete.
4 participants
Follow up of https://github.com/gravitational/teleport.e/pull/9355
Render https://kopiczko-oin--update-scim-docs.d3pp5qlev8mo18.amplifyapp.com/docs/identity-governance/integrations/okta/scim-integration/#step-12-generate-scim-token-in-teleport