mirror of
https://github.com/gravitational/teleport.git
synced 2026-10-12 02:15:01 +00:00
docs: update ig pages (#65053)
* docs: update ig pages * docs: grammar edit for sailpoint Co-authored-by: Paul Gottschling <[email protected]> --------- Co-authored-by: Paul Gottschling <[email protected]>
This commit is contained in:
co-authored by
Paul Gottschling
parent
e2dadc573e
commit
a259537444
@@ -141,7 +141,7 @@ spec:
|
||||
verbs:
|
||||
- read
|
||||
- list
|
||||
options:
|
||||
options:
|
||||
device_trust_mode: required
|
||||
require_session_mfa: true
|
||||
```
|
||||
|
||||
@@ -162,7 +162,7 @@ To allow Teleport access to Okta, the Okta API Services app created in the
|
||||
previous step must be able to verify the JWT tokens issued by Teleport. In order
|
||||
to do this, you will configure the app with the Teleport public key for Okta.
|
||||
|
||||
The procedure varies slightly depending on whether you Teleport cluster is
|
||||
The procedure varies slightly depending on whether your Teleport cluster is
|
||||
accessible over the public internet:.
|
||||
|
||||
<Tabs>
|
||||
|
||||
@@ -38,7 +38,7 @@ Navigate to the Teleport SCIM Integration page and copy the OAuth 2.0 details an
|
||||
In the SailPoint SCIM application configuration view, populate the configuration settings using the values obtained from the Teleport SCIM integration:
|
||||
* SCIM Base URL: Paste the SCIM Base URL copied from SCIM Teleport Integration page
|
||||
* Authentication Type: Pick "OAuth 2.0"
|
||||
* Token URL: Paste the Token UR copied from SCIM Teleport Integration page
|
||||
* Token URL: Paste the Token URL copied from the SCIM Teleport integration page
|
||||
* Grant Type: Pick "Client Credentials"
|
||||
* Client ID: The Client ID copied from SCIM Teleport Integration page
|
||||
|
||||
|
||||
Reference in New Issue
Block a user