You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I receive 401 response for "api/v1/employee/register" with information that no JWT token has been provided, but I don't want to provide it, because it is route with anonymous access.
The text was updated successfully, but these errors were encountered:
maciejmiara
changed the title
PR #157 broke security.yml settings
PR #157 ignores security.yml anonymous path
Apr 10, 2016
@maciejmiara Thank you for the report.
I already submitted a PR #159 that fixes the bug, it will be merged as soon as possible (hope tomorrow).
Sorry for the inconvenience.
Merged PR #157 commit 3051ad5 (Add Events::JWT_INVALID and Events::AUTHENTICATION_FAILURE listening) causes an error.
Now, even though I have following setting in security.yml:
I receive 401 response for "api/v1/employee/register" with information that no JWT token has been provided, but I don't want to provide it, because it is route with anonymous access.
The text was updated successfully, but these errors were encountered: