[v13] Okta service docs only show in enterprise and cloud. (#28069)

* Okta service docs only show in enterprise and cloud. The docs describing the Okta service now only display in the enterprise and cloud scopes. Additionally, some of the wording and variable usage was corrected in the Okta guide. * Update docs/pages/application-access/okta/guide.mdx Co-authored-by: Steven Martin <steven@goteleport.com> --------- Co-authored-by: Steven Martin <steven@goteleport.com>
gravitational · Jun 20, 2023 · d4211a1 · d4211a1
1 parent c963465
commit d4211a1
Show file tree

Hide file tree

Showing 2 changed files with 24 additions and 8 deletions.
diff --git a/docs/config.json b/docs/config.json
@@ -975,18 +975,34 @@
         {
           "title": "Protect Okta Applications and Groups (Preview)",
           "slug": "/application-access/okta/",
+          "forScopes": [
+            "enterprise",
+            "cloud"
+          ],
           "entries": [
             {
               "title": "Okta Service",
-              "slug": "/application-access/okta/guide/"
+              "slug": "/application-access/okta/guide/",
+              "forScopes": [
+                "enterprise",
+                "cloud"
+              ]
             },
             {
               "title": "Architecture",
-              "slug": "/application-access/okta/architecture/"
+              "slug": "/application-access/okta/architecture/",
+              "forScopes": [
+                "enterprise",
+                "cloud"
+              ]
             },
             {
               "title": "Reference",
-              "slug": "/application-access/okta/reference/"
+              "slug": "/application-access/okta/reference/",
+              "forScopes": [
+                "enterprise",
+                "cloud"
+              ]
             }
           ]
         },

diff --git a/docs/pages/application-access/okta/guide.mdx b/docs/pages/application-access/okta/guide.mdx
@@ -16,10 +16,10 @@ configurations to enable it.
 
 ## Prerequisites
 
-(!docs/pages/includes/edition-prereqs-tabs.mdx!)
+(!docs/pages/includes/commercial-prereqs-tabs.mdx!)
 
 - (!docs/pages/includes/tctl.mdx!)
-- An Okta organization with an [Okta API token](https://developer.okta.com/docs/guides/create-an-api-token) provisioned.
+- An Okta organization with an [Okta API token](https://developer.okta.com/docs/guides/create-an-api-token) created.
 - A running Teleport cluster with Okta login configured.
 - An instance where you will run the Okta Service. This can live anywhere
   with outbound access to Okta and must be running Linux.
@@ -30,7 +30,7 @@ Before setting up the Okta Service, you should create Okta import rules in order
 to ensure that our Okta applications are set up with appropriate labeling before
 you attempt to synchronize them. First, you'll need to get the group and application
 IDs from Okta. The easiest way to do this is to use the <Var name="okta-api-token" />
-provisioned earlier.
+that was created when when evaluating the prerequisites.
 
 To get group IDs:
 
@@ -152,8 +152,8 @@ ssh_service:
   enabled: no
 okta_service:
   enabled: yes
-  api_endpoint: <Var name="okta-endpoint-url" />
-  api_token_path: <Var name="okta-api-token-path" />
+  api_endpoint: <replace-with-okta-endpoint-url>
+  api_token_path: <replace-with-okta-api-token-path>
 ```
 
 Edit `/etc/teleport.yaml` to replace `teleport.example.com:443` with the host