Skip to content

Commit cb8040d

Browse files
Merge pull request #1192 from rackerlabs/dex-auth-updates
feat(dex): bump version to support device authorization flow
2 parents aa881b5 + cf33bf6 commit cb8040d

File tree

3 files changed

+19
-0
lines changed

3 files changed

+19
-0
lines changed

components/dex/values.yaml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,9 @@
22
# https://github.com/dexidp/helm-charts/tree/master/charts/dex#values
33
#
44

5+
image:
6+
tag: v2.44.0
7+
58
replicaCount: 1
69
config:
710
# See https://dexidp.io/docs/storage/ for more options

docs/deploy-guide/config-dex.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# Configuring Dex
2+
3+
As of Dex v2.44.0 the HTTP 302 redirects contain a `Location` header which
4+
is relative and not all clients like this in authentication flows. To workaround
5+
this easiest approach is have the ingress rewrite the URL for us.
6+
7+
In `$DEPLOY_NAME/helm-configs/dex.yaml` in the `ingress.annotations` key, add the
8+
following:
9+
10+
```yaml
11+
ingress:
12+
annotations:
13+
nginx.ingress.kubernetes.io/proxy-redirect-from: "/"
14+
nginx.ingress.kubernetes.io/proxy-redirect-to: "https://dex.your.url/"
15+
```

mkdocs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -129,6 +129,7 @@ nav:
129129
- Preparing Our Deployment:
130130
- deploy-guide/deploy-repo.md
131131
- deploy-guide/component-config.md
132+
- deploy-guide/config-dex.md
132133
- deploy-guide/auth.md
133134
- deploy-guide/config-argo-workflows.md
134135
- Starting the Deployment:

0 commit comments

Comments
 (0)