fixes "A Token was not found in the SecurityContext" error #1052
Conversation
This file contains hidden or 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
|
Why changing the formatting of the method there ? It seems like you did not change the logic at all except removing the early return |
|
You are correct. The early return was causing the "Token not found in SecurityContext" error. Now, a 403 Response is set instead. The change of formatting is because I indented everything to be inside the |
|
I don't see how the early return could be the reason of the issue. Your code is strictly equivalent as nothing is done when there is no x-wsse header. |
|
Now it sets and returns a 403 response if there is no x-wsse header. Before, it returned without setting a token or a response, which caused the error. |
weaverryan
added a commit
that referenced
this pull request
Feb 8, 2012
…provider-cookbook-article-2.0 fixes "A Token was not found in the SecurityContext" error
|
Merged! Thanks! |
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.
Following Ryan's instructions outlined here:
Submitting a pull request to fix the 2.0 branch first. 2.1 commit to follow as soon as this is merged in.