Open
Conversation
yhoztak
reviewed
Feb 18, 2026
| - Authentication Mode: HTTP Header | ||
|
|
||
| Please contact the Corgea support team to obtain the necessary API token. | ||
| You can copy the SCIM API token from the SSO configuration screen: |
Contributor
There was a problem hiding this comment.
I already merged #70. It'd be great if it could have taken a screenshot and update
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Updated the SSO SCIM provider configuration docs to reflect SCIM being enabled by default and to explain how admins can copy the SCIM API token from the SSO configuration screen. This removes the prior support-contact step and aligns the steps with the new UI behavior.