-
Notifications
You must be signed in to change notification settings - Fork 59
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
Unexpected result #63
Comments
Hi Jonatas, thanks for getting in touch! It sounds to me that your API is not stateless... Do let me know (perhaps provide some code snippets) how you get on! Kind regards, |
P.S. If the WSSE header is not present, the WSSE authentication bundle does not demy the request - it just doesn't kick in WSSE authentication. There is a PR (#42) open to make this behaviour possible, but I'd prefer it to be configurable... Thanks in advance for your feedback! |
I test in NelmioAPIDoc Sandbox, direct request. Not have any code. |
Somewhat related, shouldn't the example code in the docs have the user set their firewall to stateless? I believe that's a requirement for someone who wants to use an authentication provider like this. |
Hi @bkosborne, that is a good suggestion - WSSE auth is stateless, but making that clearer in the firewall makes sense... Would you mind sensing over a quick PR? Kind regards, |
My security file: security:
|
Hello,
what is happening is the following.
I'm testing the REST api in sandbox NelmioDoc.
The first time I open the browser, I try the request without sending the wsse header and returns 401, expected result.
When I add the header WSSE, returns 200, expected result.
When I make a new request with the same header, returns 401, expected result.
Now the possible problem, when I remove the header and make the request again, returns 200, not expected.
Why does it happen?
Should not deny request, and the header wsse not exist?
The text was updated successfully, but these errors were encountered: