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: Document SSO expiry option #5552

Merged
merged 5 commits into from
Apr 8, 2021
Merged
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
1 change: 1 addition & 0 deletions USERS.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,7 @@ Currently, the following organizations are **officially** using Argo Workflows:
1. [SAS](https://www.sas.com/)
1. [Schlumberger](https://slb.com/)
1. [SegmentStream](https://segmentstream.com)
1. [Sendible](https://sendible.com)
tico24 marked this conversation as resolved.
Show resolved Hide resolved
1. [Sidecar Technologies](https://hello.getsidecar.com/)
1. [Softonic](https://hello.softonic.com/)
1. [Sohu](https://www.sohu.com/)
Expand Down
14 changes: 14 additions & 0 deletions docs/argo-server-sso.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,18 @@ If no rule matches, we deny the user access.

The precedence must be the lowest of all your service accounts.

## SSO Login Time

> v2.12 and after

By default, your SSO session will expire after 10 hours. You can change this by adding a sessionExpiry value to your [workflow-controller-configmap.yaml](workflow-controller-configmap.yaml) under the SSO heading.

```yaml
sso:
# Expiry defines how long your login is valid for in hours. (optional)
sessionExpiry: 240h
```

## Sharing the Argo CD Dex Instance using Oauth2

It is possible to have the Argo Workflows Server use the Argo CD Dex instance for SSO, for instance if you use Okta with SAML which cannot integrate with Argo Workflows directly. In order to make this happen, you will need the following:
Expand Down Expand Up @@ -149,6 +161,8 @@ What this might look like in your chart configuration:
- --auth-mode=sso
sso:
issuer: https://argo-cd.mydomain.com/api/dex
# sessionExpiry defines how long your login is valid for in hours. (optional, default: 10h)
sessionExpiry: 240h
clientId:
name: argo-workflows-sso
key: client-id
Expand Down
3 changes: 3 additions & 0 deletions docs/workflow-controller-configmap.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -267,6 +267,9 @@ data:
sso: |
# This is the root URL of the OIDC provider (required).
issuer: https://issuer.root.url/
# This defines how long your login is valid for (in hours). (optional)
# If omitted, defaults to 10h. Example below is 10 days.
sessionExpiry: 240h
# This is name of the secret and the key in it that contain OIDC client
# ID issued to the application by the provider (required).
clientId:
Expand Down