yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-08-18 14:06:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Okta documentation (#8433)

Browse Source
This commit is contained in:
Nahuel 2022-10-29 22:04:01 +02:00 committed by GitHub
parent 3ed6ad8456
commit 02da18a5c0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
openmetadata-docs/content/deployment/security/okta/index.md
View File

@ -50,8 +50,8 @@ This document will explain how to create an Okta app and configure it for OAuth.
- The app is now configured.
<Image src="/images/deployment/security/okta/app-is-configured.png" alt="app-is-configured"/>
### Step 4: Add Authorization Server to get the Issuer URL
It is recommended to create a separate authorization server for different applications. The authorization server needs an endpoint, which'll be the Issuer URL.
### Step 4: Add Authorization Server to get the Issuer URL (optional)
This step and the following ones are not mandatory. It is recommended to create a separate authorization server for different applications. The authorization server needs an endpoint, which'll be the Issuer URL.
- Click on **Security -> API** in the left navigation panel.
<Image src="/images/deployment/security/okta/click-security-api.png" alt="click-security-api"/>
@ -65,14 +65,14 @@ It is recommended to create a separate authorization server for different applic
This will generate the Issuer URL.
### Step 5: Change the Issuer URL from Dynamic to Okta URL
### Step 5: Change the Issuer URL from Dynamic to Okta URL (optional)
Once the Authorization Server has been added, navigate to Security >> API >> Authorization Servers and click on the authorization server created in the previous step.
<Image src="/images/deployment/security/okta/click-auth-server-from-prev-step.png" alt="click-auth-server-from-prev-step"/>
The Issuer URL shows up as Dynamic by default. Change the Issuer URL to Okta URL and save the changes.
<Image src="/images/deployment/security/okta/change-issuer-url.png" alt="change-issuer-url"/>
### Step 6: Create a Default Scope
### Step 6: Create a Default Scope (optional)
- To create a default scope from **Security -> API**, click on the required **Authorization Server**.
<Image src="/images/deployment/security/okta/click-req-auth-server.png" alt="click-req-auth-server"/>
@ -83,7 +83,7 @@ The Issuer URL shows up as Dynamic by default. Change the Issuer URL to Okta URL
- Set as a **Default Scope**.
<Image src="/images/deployment/security/okta/set-default-scope.png" alt="set-default-scope"/>
## Step 7: Add New Access Policy and Rule
## Step 7: Add New Access Policy and Rule (optional)
- From **Security -> API**, click on the required **Authorization Server**
- Navigate to the **Access Policies Tab**
- Click on **Add New Access Policy**
@ -97,7 +97,7 @@ The Issuer URL shows up as Dynamic by default. Change the Issuer URL to Okta URL
- Click on **Create Rule** to save the changes.
<Image src="/images/deployment/security/okta/add-rule.png" alt="add-rule"/>
### Step 8: Where to Find the Credentials
### Step 8: Where to Find the Credentials (optional)
- Once the app is configured, the **Client ID** can be used.
- You can also go to **Application -> Application** as in step 2.
- You should be able to see your application in the list.