-
Notifications
You must be signed in to change notification settings - Fork 5
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
Require step up authentication for Recovery Token create and delete actions #264
Merged
MKodde
merged 6 commits into
feature/self-asserted-tokens
from
feature/sat-require-step-up-for-rt-create-delete
Jul 4, 2022
Merged
Require step up authentication for Recovery Token create and delete actions #264
MKodde
merged 6 commits into
feature/self-asserted-tokens
from
feature/sat-require-step-up-for-rt-create-delete
Jul 4, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
MKodde
commented
Jun 23, 2022
•
edited
Loading
edited
- In preparation, the SAT controller was cleaned up by segregating the dedicated RT actions from the registration related actions
- The 'test' authentication consume assertion endpoint was re-re-used to also serve self-asserted recovery token step up authentications. I considered creating a new SFO SP for this. But that would get complex really soon. The step up bundle does not support multiple ACS locations either. So this solution seemed to fit best.
6fb761c
to
67bc092
Compare
1cc3e17
to
0d33d98
Compare
This was previously set to 2, eliminating self-asserted tokens from the token test in GW.
0d33d98
to
9fc2366
Compare
52c42a3
to
5285e07
Compare
The SAT registration and dedicated Recovery token actions have been decoupled into separate controllers. The shared logic is placed in a trait. For now the constructors of both controllers are the same, and they now live in the trait. All controller actions have been given a developer friendly description with a high level description of what the action is responsible for.
The RT state storage is used heavily to indicate when step up is given. And to verify when the user still needs to give step-up to perform create and delete actions on the Recovert Tokens.
5285e07
to
a9925e2
Compare
8d99ecf
to
5da7f21
Compare
pablothedude
approved these changes
Jun 29, 2022
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.
Thanks for adding the extensive documentation!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.