-
Notifications
You must be signed in to change notification settings - Fork 9
CDM-243: Add MFA to TemporarySessionData LOGINIDENTS operation #503
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
Conversation
All the other changes in this PR flow out of that single change. eesh. TODO: test the UITokens for MFA status once it's exposed in the API layer.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #503 +/- ##
==========================================
Coverage 93.41% 93.42%
- Complexity 2167 2169 +2
==========================================
Files 129 129
Lines 7626 7636 +10
Branches 1181 1184 +3
==========================================
+ Hits 7124 7134 +10
Misses 459 459
Partials 43 43 🚀 New features to boost your workflow:
|
| assertThat("incorrect state", ti.getOAuth2State(), is(ES)); | ||
| assertThat("incorrect pkce", ti.getPKCECodeVerifier(), is(ES)); | ||
| assertThat("incorrect user", ti.getUser(), is(Optional.empty())); | ||
| assertThat("incorrect user", ti.getUser(), is(opt())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would not immediately know opt() vs Optional.empty meant an empty optional, but I also am not steeped in Java norms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's just personal short hand since it's used over and over in these tests
dauglyon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test changes seem good, I didn't see anything unexpected except the test looping logic but that makes sense. Non-test changes are as expected. Not sure about the LoginState comment but assume it's a good idea given mfa state is indeed a type of login state. Should be good to merge!
|
The login state is just referring to the endpoint where the user gets to choose what account to log into (or for KBase, affirms they're logging into the right account. As such, MFA status doesn't really matter unless we wanted to stop the login flow right there or something |
|
It doesn't hurt to have it though, could be used to give feedback to the user that their MFA state is as expected (or not) |
All the other changes in this PR flow out of that single change. eesh.
TODO: test the UITokens for MFA status once it's exposed in the API layer.
Turning whitespace off makes the review a lot simpler