Basanth Jenu H B

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 easily...

Got it, So even if we move to secret based authentication, The cluster admin of cluster-1 has to manually create a token, add it to a secret and give it...

Ok, fair @alexec to your original question, `Would you use it in your projects?`, Don't think so, the existing model works as of now for us.

@alexec can we store in a K8s secret object. it will be just another key in the secret

yup. Ideally the combination should be ``` Converter Generator ``` so when `T` is retrieved from database, `T` can be converted to `U` using the converter But now, we are...

@lukaseder any updates on this ?

We have added new feature related to SSO https://github.com/argoproj/argo-workflows/blob/master/docs/argo-server-sso.md#sso-rbac-namespace-delegation @HouseoLogy @andrewm-aero Would this help in your use case

So `ListArchivedWorkflowsRequest` is implemented differently. It doesn't have a namespace parameter. Namespace is passed as a `FieldSelector` Hence currently this will not work so to fix this, 2 options 1....

Other requests like `RetryArchivedWorkflowRequest`, `ResubmitArchivedWorkflowRequest` have a namespace parameter. Not sure why `ListArchivedWorkflowsRequest` was implemented differently.

We can support, just that the request needs to be modified to add a namespace parameter. For ListArchivedWorkflowsRequest and couple of others. Shall i make a PR with this approach...