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/06/28 14:28:00 UTC

[jira] [Commented] (SYNCOPE-1129) Third Party JWT SSO integration

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

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

Commit 94708a3eed564f6bc33953075d7ac423a4ec167d in syncope's branch refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=94708a3 ]

[SYNCOPE-1129] New interface JWTSSOProvider with default impl SyncopeJWTSSOProvider + docs


> Third Party JWT SSO integration
> -------------------------------
>
>                 Key: SYNCOPE-1129
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1129
>             Project: Syncope
>          Issue Type: New Feature
>          Components: core
>            Reporter: Colm O hEigeartaigh
>            Assignee: Francesco Chicchiriccò
>             Fix For: 2.0.4, 2.1.0
>
>
> This task is to support SSO using third party JWT tokens.
> It involves two tasks:
> a) Create a new interface extending JwsSignatureVerifier to provide a method to resolve a JWT subject into Syncope username (known user).
> b) When processing a received token, if the issuer is different from the known issuer ("jwtIssuer" in security.properties), then instead of retrieving the default jwsSignatureVerifier implementation, the authentication component will enable the ClassPathScanImplementationLookup to dynamically discover an implementation of the interface above.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)