-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Docs: Update SCIM enrollment for OIN #69415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kopiczko
wants to merge
4
commits into
master
Choose a base branch
from
kopiczko/oin__update_scim_docs
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -66,11 +66,11 @@ This step assumes you are still in the **Okta Integration** configuration wizard | |
| 1. Navigate to **Zero Trust Access** on the left sidebar, then select **Integrations** and click on the **Okta** row. | ||
| 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. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "new SCIM configuration" needs an article. |
||
|
|
||
| 1. Copy the generated **Bearer Token** and store it for later. It will be required for the Okta Teleport app configuration. | ||
| </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. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
|
|
||
|  | ||
|
|
||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're discouraging adding new images to the
gravitational/teleportrepo 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CC @zmb3 to make sure this is okay, since I know we've talked about images and repo size in the past.