LoricAndre
LoricAndre
You're right about the SSO+Token, the previous code made them incompatible. It is fixed now, and I added a test to verify it.
The issue is open (https://github.com/argoproj/argo-workflows/issues/9090)
@alexec about the self-serve part, implementing this would then require secrets in every workflow's namespace, instead of just the server's. This seems pretty heavy to me, I can implement a...
I'm not sure I get what you mean by 'user namespace', since there is no user with this auth method. I can use the request's namespace instead, but this doesn't...
The use case is automatically managing workflows from a different cluster (in our case, using another argo-workflow deplyment)
> It is not self-serve. What about looking up the secret from the requests namespace? @basanthjenuhb and @terrytangyuan both did something similar recently. **I'm not sure what you mean by...
The namespace and service account used are the server's, which makes it close to a server authentication mode but requiring a token in that sense
> Apologies, I m not sure if I understand the use-case. Currently Argo workflows supports token authentication, which are generated by secrets related to service accounts. This allows us to...
This is really designed for automation, and afaik it is not that simple to transfer the token gotten from one cluster to another, but it can be trivial to set...
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....