Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
EKS Capabilities ArgoCD deployment should support authentication with other identity providers than AWS Identity Center.
Which service(s) is this request for?
EKS capabilities
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I would like to be able to login with Okta SSO, which is normally supported with ArgoCD.
I am aware AWS Identity Center can be configured to sync with third party SSO providers, but it does not work same way as native support. Using "Login via SSO" button does not redirect to Okta login page. It works when already logged in to AWS SSO Portal. On Okta, application is shown as "AWS IAM Identity Center", not ArgoCD, which creates confusion for users.
Are you currently working around this issue?
Currently using self managed ArgoCD, I plan to migrate EKS Capabilities ArgoCD on all clusters once all requirements are met.
Additional context
Attachments
Community Note
Tell us about your request
EKS Capabilities ArgoCD deployment should support authentication with other identity providers than AWS Identity Center.
Which service(s) is this request for?
EKS capabilities
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I would like to be able to login with Okta SSO, which is normally supported with ArgoCD.
I am aware AWS Identity Center can be configured to sync with third party SSO providers, but it does not work same way as native support. Using "Login via SSO" button does not redirect to Okta login page. It works when already logged in to AWS SSO Portal. On Okta, application is shown as "AWS IAM Identity Center", not ArgoCD, which creates confusion for users.
Are you currently working around this issue?
Currently using self managed ArgoCD, I plan to migrate EKS Capabilities ArgoCD on all clusters once all requirements are met.
Additional context
Attachments