From 5a502199f1e02f9228c49d921d354be814a047aa Mon Sep 17 00:00:00 2001 From: msuthar-splunk <77360432+msuthar-splunk@users.noreply.github.com> Date: Wed, 9 Mar 2022 11:53:13 +1100 Subject: [PATCH] docs: Update okta instructions (#6388) - data.oicd has no effect on the integration - SSO flow did not initiate without putting the URL for argocd at `data.url` in `argocd-cm.yaml`. This is specified in the keycloak integration instructions as well. Signed-off-by: Mit Suthar --- docs/operator-manual/user-management/okta.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/operator-manual/user-management/okta.md b/docs/operator-manual/user-management/okta.md index ffec1e8eb8e3b..09d7099d19954 100644 --- a/docs/operator-manual/user-management/okta.md +++ b/docs/operator-manual/user-management/okta.md @@ -19,7 +19,15 @@ A working Single Sign-On configuration using Okta via at least two methods was a * ![Okta SAML App 2](../../assets/saml-2.png) 1. Click `View setup instructions` after creating the application in Okta. * ![Okta SAML App 3](../../assets/saml-3.png) -1. Copy the SSO URL to the `argocd-cm` in the data.oicd +1. Copy the Argo CD URL to the `argocd-cm` in the data.url + + +```yaml +data: + url: https://argocd.example.com +``` + + 1. Download the CA certificate to use in the `argocd-cm` configuration. * If you are using this in the caData field, you will need to pass the entire certificate (including `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----` stanzas) through base64 encoding, for example, `base64 my_cert.pem`. * If you are using the ca field and storing the CA certificate separately as a secret, you will need to mount the secret to the `dex` container in the `argocd-dex-server` Deployment.