Skip to content
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

Reusing Okta Session ID #83

Merged
merged 1 commit into from
Mar 2, 2018
Merged

Conversation

smashling
Copy link
Contributor

Problem Statement

It is required that MFA must be used every time a new profile is made or refreshed.

Solution

The Session ID cookie is saved and reused so that the session will refresh as long as the session is still valid.

Copy link
Contributor

@AlainODea AlainODea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and validated. @mraible this is ready to merge.

@smashling this is an incredible user experience boost. Awesome work 🎉

@atifrasheed79
Copy link

Gents, sorry couldn't find this in documentation and I have tried various utils available in .okta/bin but couldn't find much help as how can I switch my role within the same session.
When I authenticate via okta, I am presented with multiple roles, but after selecting one, I can't selection another within the same authenticated session.
I just upgraded myself to 2.0.0, was using 1.0.12 probably and in the previous version awscli sts get-caller-identity always started a new auth session. The new version does use the existing auth session but I couldn't find an option to change my role.
Please advise!

P.S. I am getting a java exception when I try to work with okta verify (push). It was working fine in the older version. I will raise a separate ticket for this.

@smashling
Copy link
Contributor Author

smashling commented Apr 11, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants