[
https://issues.apache.org/jira/browse/CXF-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CXF-7006.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.0.11
3.1.8
3.2.0
commit
http://git-wip-us.apache.org/repos/asf/cxf/commit/395acbd2 for master
http://git-wip-us.apache.org/repos/asf/cxf/commit/3c19fac2 for 3.1.x-fixes
http://git-wip-us.apache.org/repos/asf/cxf/commit/8918a31c for 3.0.x-fixes
> add an util method in AuthorizationUtils which can take AuthorizationFailure
> cause
> ----------------------------------------------------------------------------------
>
> Key: CXF-7006
> URL: https://issues.apache.org/jira/browse/CXF-7006
> Project: CXF
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 3.2.0, 3.1.8, 3.0.11
>
>
> though by default we just return a 401 without any message to say why the
> authorization failed for more security reason, in some cases like in Customer
> AccessTokenValidatorService they may wanna return a 401 with entity message
> like "token expired" which can bring back more info. We better extend
> AuthorizationUtils a bit to add the method which can take
> authorizationFailure cause and build response accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
