You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/05 08:18:00 UTC
[jira] [Commented] (SYNCOPE-1149) Access token still required for
the third party JWT SSO integration scenario
[ https://issues.apache.org/jira/browse/SYNCOPE-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074400#comment-16074400 ]
ASF subversion and git services commented on SYNCOPE-1149:
----------------------------------------------------------
Commit 0f5116c2fc4fa175ed0b7062dad000fa8c9f46d6 in syncope's branch refs/heads/master from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=0f5116c ]
SYNCOPE-1149 - Adding @Ignore'd test for this feature
> Access token still required for the third party JWT SSO integration scenario
> ----------------------------------------------------------------------------
>
> Key: SYNCOPE-1149
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1149
> Project: Syncope
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Colm O hEigeartaigh
> Fix For: 2.0.5, 2.1.0
>
>
> When trying to invoke on Syncope with a third-party JWT, the code in AuthDataAccessor.authenticate still errors if no access token is found:
> AccessToken accessToken = accessTokenDAO.find(authentication.getClaims().getTokenId());
> if (accessToken == null) {
> throw new AuthenticationCredentialsNotFoundException(
> "Could not find JWT " + authentication.getClaims().getTokenId());
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)