[
https://issues.apache.org/jira/browse/CXF-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15787372#comment-15787372
]
ASF GitHub Bot commented on CXF-7201:
-------------------------------------
GitHub user elfogre opened a pull request:
https://github.com/apache/cxf/pull/218
[CXF-7201] Correctly format UserInfo response when no signature or
encryption is used.
Create Json UserInfo with JwtUtils.claimsToJson when no signature or
encryption is Used.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/elfogre/cxf master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/218.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #218
----
commit 5f2623068d80661da2c44bea6fe3d9c203c34dd7
Author: Jose Escobar <[email protected]>
Date: 2016-12-30T09:57:08Z
[CXF-7201] Correctly format UserInfo response when no signature or
encryption is used.
----
> Incorrect JSON return in openId connect UserInfo when no signature or
> encryption
> --------------------------------------------------------------------------------
>
> Key: CXF-7201
> URL: https://issues.apache.org/jira/browse/CXF-7201
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS Security
> Affects Versions: 3.1.9
> Reporter: Jose Escobar
> Priority: Minor
> Labels: jwt, openid
>
> Hello,
> I'm using your org.apache.cxf.rs.security.oidc.idp.UserInfoService tu publish
> an OpenId connect UserInfo service. When returned JWT requires signature or
> encryption I get a correctly formatted JWT, but when no signature or
> encryption is required, returned JSON is not correctly formatted.
> Problem occurs because on the second scenario, JSON marshal is done out of
> scope of cxf jose jwt (by default json marshaller). On signature or encrypted
> JWT, JwtUtils.claimsToJson is used and result is OK.
> I've resolve this using a custom UserInfoService. I'm going to send a pull
> request with a fix hoping it could be useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
