oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stein Welberg (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OLTU-178) initial responseCode not set in the OAuthProblemException
Date Tue, 23 Feb 2016 08:16:18 GMT

     [ https://issues.apache.org/jira/browse/OLTU-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stein Welberg resolved OLTU-178.
--------------------------------
    Resolution: Fixed

Issue is fixed. The {{OAuthClientValidator#validateErrorResponse}} now sets the response code
correctly.

> 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
>
> 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)

Mime
View raw message