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
{{ message }}
This repository was archived by the owner on May 31, 2022. It is now read-only.
At the moment I'm using an implementation of a ConsumerDetailsService to look up consumer keys. If a consumer key has not been found, then I want to throw a InvalidOAuthParametersException and for the server to respond with a 401 Unauthorized exception.
However in the OAuthProcessingFilterEntryPoint, if an InvalidOAuthParametersException is thrown this is mapped to a 400 Bad Request response:
At the moment I'm using an implementation of a ConsumerDetailsService to look up consumer keys. If a consumer key has not been found, then I want to throw a InvalidOAuthParametersException and for the server to respond with a 401 Unauthorized exception.
However in the OAuthProcessingFilterEntryPoint, if an InvalidOAuthParametersException is thrown this is mapped to a 400 Bad Request response:
According to the HTTP specification, a 400 response should be used when:
And a 401 response should be used when:
This filter should be updated to use a 401 response.