JASPIC ServerAuthModule and ServerAuthContext spec compliance fixes #375
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
This contains two sets of fixes: - The SAMs no longer return SUCCESS with emtpy principals for mandatory authentication - The ServerAuthContext sets up two SAM module instances to satisfy the spec requirement that the mandatory flag can be accessed from the requestPolicy The first fix is important, as currently the tests fail to return proper http status codes for unathenticated protected resources on multiple app servers. The second fix is just for complying with the letter of the spec, as the requestPolicy is not actually used in any of the current tests.
|
I've glanced over the PR and it looks good at first sight, but I'm very busy now with JSF 2.3 (final day before it closes). But haven't forgotten about this PR ;) Will look at it soon in more detail. Thanks for now! |
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.
This contains two sets of fixes:
authentication
spec requirement that the mandatory flag can be accessed from the
requestPolicy
The first fix is important, as currently the tests fail to return proper
http status codes for unathenticated protected resources on multiple app
servers.
The second fix is just for complying with the letter of the spec, as the
requestPolicy is not actually used in any of the current tests.