Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix aws sso documentation #20681

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified docs/assets/identity-center-1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
23 changes: 17 additions & 6 deletions docs/operator-manual/user-management/identity-center.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,15 @@ A working Single Sign-On configuration using Identity Center (AWS SSO) has been
## SAML (with Dex)

1. Create a new SAML application in Identity Center and download the certificate.
* ![Identity Center SAML App 1](../../assets/identity-center-1.png)
* ![Identity Center SAML App 2](../../assets/identity-center-2.png)

![Identity Center SAML App 1](../../assets/identity-center-1.png)

![Identity Center SAML App 2](../../assets/identity-center-2.png)

Comment on lines +13 to +17
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if these changes were intentional, if not we should probably undo these

2. Click `Assign Users` after creating the application in Identity Center, and select the users or user groups you wish to grant access to this application.
* ![Identity Center SAML App 3](../../assets/identity-center-3.png)

![Identity Center SAML App 3](../../assets/identity-center-3.png)

3. Copy the Argo CD URL into the `data.url` field in the `argocd-cm` ConfigMap.

data:
Expand All @@ -24,15 +29,20 @@ A working Single Sign-On configuration using Identity Center (AWS SSO) has been
!!! note "Group attribute mapping is not officially!"
Group attribute mapping is not officially supported in the AWS docs, however the workaround is currently working.

* ![Identity Center SAML App 4](../../assets/identity-center-4.png)
* ![Identity Center SAML App 5](../../assets/identity-center-5.png)
![Identity Center SAML App 4](../../assets/identity-center-4.png)

![Identity Center SAML App 5](../../assets/identity-center-5.png)

<!-- markdownlint-enable MD046 -->

5. Download the CA certificate to use in the `argocd-cm` configuration.

* If using the `caData` field, you'll need to base64-encode the entire certificate, including the `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----` stanzas (e.g., `base64 my_cert.pem`).

* If using the `ca` field and storing the CA certificate separately as a secret, you will need to mount the secret onto the `dex` container in the `argocd-dex-server` Deployment.
* ![Identity Center SAML App 6](../../assets/identity-center-6.png)

![Identity Center SAML App 6](../../assets/identity-center-6.png)

6. Edit the `argocd-cm` and configure the `data.dex.config` section:

<!-- markdownlint-disable MD046 -->
Expand Down Expand Up @@ -60,6 +70,7 @@ dex.config: |
<!-- markdownlint-enable MD046 -->

### Connect Identity Center Groups to Argo CD Roles

Argo CD recognizes user memberships in Identity Center groups that match the **Group Attribute Statements** regex.

In the example above, the regex `argocd-*` is used, making Argo CD aware of a group named `argocd-admins`.
Expand Down