-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
RBAC enabled but not restricting user #8310
Comments
Can you be more specific? For example, do you go into the UI, and are allowed to update a workflow? What is your Kubernetes provider? Does it both support and have RBAC enabled correctly? E.g. Docker for Desktop does not support RBAC. Certain cloud configurations don't either. |
Hi, thank you for that quick answer. I can get into the UI without issues and the SSO SA is correctly assigned, which I can see in the User tab. The issue is that once logged in, I can create and submit workflows without any error. My Kubernetes provider is Azure AKS, and RBAC is enabled and used successfully in other projects. |
I think this is most likely to be mis-configuration, so I'm don't want to invest too much time until we've checked that.
If that fails, please book 30m via the new issue link. |
Attempted to repro, failed:
|
|
It is, my email is associated with:
Impersonation is disabled on the cluster, I cannot test this. |
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: argo:operator
rules:
- apiGroups:
- argoproj.io
resources:
- workflowtemplates
resourceNames:
- ci-k8s
- ci-protobuf
- ci-python
verbs:
- get
- list
- watch
- apiGroups:
- ""
resources:
- pods
verbs:
- get
- list
- watch
- apiGroups:
- ""
resources:
- pods/log
verbs:
- get
- list
- watch
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: "tmp-sso-argo:operator"
subjects:
- kind: ServiceAccount
name: tmp-sso-argo-workflows
namespace: argo
roleRef:
kind: Role
name: argo:operator
apiGroup: rbac.authorization.k8s.io
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: "tmp-sso-argo-workflows"
annotations:
workflows.argoproj.io/rbac-rule: "'*****:****' in groups"
workflows.argoproj.io/rbac-rule-precedence: "0"
secrets:
- name: github-sso-argo-workflows |
@qtheya Does your comment(#8310 (comment)) mean that you succeeded to reproduce the bug? |
Yes |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
anyone can share the actual groups in userprofile and the actual 'something' in groups condition |
Checklist
Summary
What happened/what you expected to happen?
After setting up SSO and RBAC, SSO is working and assigning me the right ServiceAccount, but the rights I have on the server are more open than the associated role gives.
This is my RBAC SA/Role/RoleBinding:
What version are you running?
v3.3.1
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
Any workflow
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: