[
https://issues.apache.org/jira/browse/CXF-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417804#comment-13417804
]
Sergey Beryozkin commented on CXF-4428:
---------------------------------------
Update: "report.failure.details" and "report.failure.details.as.header"
contextual properties should be used instead.
"report.failure.details.as.header" can be set to get the problem reported as
the "oauth_problem" header (as apparently LinkedIn did), otherwise it is in the
response body
> [OAuth1.0] allow to set response codes when throwing exception from
> OAuthDataProvider implementation.
> -----------------------------------------------------------------------------------------------------
>
> Key: CXF-4428
> URL: https://issues.apache.org/jira/browse/CXF-4428
> Project: CXF
> Issue Type: Wish
> Components: JAX-RS Security
> Affects Versions: 2.6.1
> Reporter: Evgeni Kisel
> Assignee: Sergey Beryozkin
> Fix For: 2.6.2, 2.7.0
>
>
> Currently OAuthDataProvider interface support throwing OAuthServiceException.
> But handlers (request token, authorize, access token) catch this exception
> and always return response status 500.
> I think it will be better to allow setting custom response statuses and add
> proper handling for this exception type.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
