From fe3dd4843337a8fd97384b006849f812073b3d05 Mon Sep 17 00:00:00 2001
From: Jim Kalafut <jkalafut@hashicorp.com>
Date: Wed, 6 Jan 2021 10:05:23 -0800
Subject: [PATCH] Make example Okta creds more obviously fake (#10639)

---
 website/pages/docs/auth/okta.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/docs/auth/okta.mdx b/website/pages/docs/auth/okta.mdx
index 8a10fe440f68..c43e82e338b1 100644
--- a/website/pages/docs/auth/okta.mdx
+++ b/website/pages/docs/auth/okta.mdx
@@ -43,7 +43,7 @@ The response will contain a token at `auth.client_token`:
 ```json
 {
   "auth": {
-    "client_token": "c4f280f6-fdb2-18eb-89d3-589e2e834cdb",
+    "client_token": "abcd1234-7890...",
     "policies": ["admins"],
     "metadata": {
       "username": "mitchellh"
@@ -72,7 +72,7 @@ $ vault auth enable okta
 $ vault write auth/okta/config \
    base_url="okta.com" \
    org_name="dev-123456" \
-   api_token="00KzlTNCqDf0enpQKYSAYUt88KHqXax6dT11xEZz_g"
+   api_token="00abcxyz..."
 ```
 
 \*\*If no token is supplied, Vault will function, but only locally configured