You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oltu.apache.org by "Jasha Joachimsthal (JIRA)" <ji...@apache.org> on 2016/03/02 18:47:18 UTC
[jira] [Updated] (OLTU-178) initial responseCode not set in the
OAuthProblemException
[ https://issues.apache.org/jira/browse/OLTU-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jasha Joachimsthal updated OLTU-178:
------------------------------------
Fix Version/s: oauth2-1.0.2
> initial responseCode not set in the OAuthProblemException
> ---------------------------------------------------------
>
> Key: OLTU-178
> URL: https://issues.apache.org/jira/browse/OLTU-178
> Project: Apache Oltu
> Issue Type: Bug
> Components: oauth2-client
> Affects Versions: oauth2-1.0.0
> Reporter: Plaindoux
> Fix For: oauth2-1.0.2
>
>
> In the {{OAuthClientValidator#validateErrorResponse()}} method the responseCode is not set when a custom exception is built. As a consequence it always returns a bad request status (400).
> This value is correctly set in the OAuthClientResponse but it's lost later in the call stack. In order to fix it {{OAuthClientValidator#responseStatus(int)}} can be call in the validateErrorResponse method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)