[archived] "Argo Server Auth Mode" docs discussion #10627
Replies: 5 comments 4 replies
-
I believe that's out of date since https://argoproj.github.io/argo-workflows/argo-server-sso/#sso-rbac seems to describe how to map OIDC groups to service accounts. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
I'm trying to configure kong as ingress with: apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
konghq.com/protocols: "https"
konghq.com/https-redirect-status-code: "308"
konghq.com/strip-path: "true"
name: argo-server-ingress
namespace: cicd
spec:
ingressClassName: kong
rules:
- host: www.example.com
http:
paths:
- backend:
service:
name: argo-server
port:
number: 2746
path: /argo
pathType: ImplementationSpecific In argo server I configure: env:
- name: BASE_HREF
value: /argo/ and not work. |
Beta Was this translation helpful? Give feedback.
-
For user-friendliness, might be nice not to have to add 'Bearer ' before the client token when pasting into login page... |
Beta Was this translation helpful? Give feedback.
-
I don't understand how the RBAC works in Argo Server. I am using the client mode, I created a dummy service account and a token in an completeley unrelated namespace, and used it to authenticate with the Argo server. That not only worked, but I can do everything with it: run/delete workflows... And this service account does not have any roles or any permission. |
Beta Was this translation helpful? Give feedback.
-
en/latest/argo-server-auth-mode/
https://argo-workflows.readthedocs.io/en/latest/argo-server-auth-mode/
Beta Was this translation helpful? Give feedback.
All reactions