-
Notifications
You must be signed in to change notification settings - Fork 35
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
AWS SSO Support (was IndexError: list index out of range) #128
Comments
@korporationcl Keyman isn't built for Okta's AWS SSO module; it works with AWS IAM Federation which is why that URL doesn't match. They're different integrations and don't operate the same. |
Reopening, I have support for AWS SSO in the works. It'll take a bit to get it parity with the main features that interact with Okta I think but I have the first stages already working. |
Thanks mate!
…On Thu, Jun 30, 2022, 12:11 Nathan V ***@***.***> wrote:
Reopening, I have support for AWS SSO in the works. It'll take a bit to
get it parity with the main features that interact with Okta I think but I
have the first stages already working.
—
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKSLEURDV5LRKLDD3N6DN73VRT65PANCNFSM5TE6E7PA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@nathan-v I'm looking for a CLI tool that supports the AWS SSO app, but so far no one has implemented it and was considering doing it by myself. Can you maybe already share your current status of the implementation in a branch, so I can test and perhaps contribute? |
@zwo-bot I'll try to push something soonish. I have the SSO part working but haven't had time since to get that integrated into the rest of the automation. Work priorities shifted but I hope to have some time soon. |
Describe the bug
Hey @nathan-v, I was looking today into your tool but I'm hitting another issue right now that is related to:
Noticed I had to rebuild the package since the AWS SSO integration in Okta has a different name (maybe Okta changed this without telling anyone)
I'm happy to provide and help to troubleshoot the issue!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Not to crash
Host (please complete the following information):
The text was updated successfully, but these errors were encountered: