syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-1149) Access token still required for the third party JWT SSO integration scenario
Date Wed, 05 Jul 2017 08:19:00 GMT

    [ https://issues.apache.org/jira/browse/SYNCOPE-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074401#comment-16074401
] 

ASF subversion and git services commented on SYNCOPE-1149:
----------------------------------------------------------

Commit 647d03ad14a7278d70e0da836f730235a7402613 in syncope's branch refs/heads/2_0_X from
[~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=647d03a ]

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)

Mime
View raw message