From 02da18a5c0671efcb965b9985afe4dcbdfb71d98 Mon Sep 17 00:00:00 2001
From: Nahuel <nahuel@getcollate.io>
Date: Sat, 29 Oct 2022 22:04:01 +0200
Subject: [PATCH] Update Okta documentation (#8433)

---
 .../content/deployment/security/okta/index.md        | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/openmetadata-docs/content/deployment/security/okta/index.md b/openmetadata-docs/content/deployment/security/okta/index.md
index e3c84261ef6..fb4324099d1 100644
--- a/openmetadata-docs/content/deployment/security/okta/index.md
+++ b/openmetadata-docs/content/deployment/security/okta/index.md
@@ -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.