[
https://issues.apache.org/jira/browse/SYNCOPE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650238#comment-16650238
]
ASF subversion and git services commented on SYNCOPE-1384:
----------------------------------------------------------
Commit fd24dd8b49a47f7868f0f995c0d180e559b4896b in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=fd24dd8 ]
[SYNCOPE-1384] Add RequestedAuthnContextProvider
> SAML 2.0: Allow to customize RequestedAuthnContext for a given Service
> Provider
> -------------------------------------------------------------------------------
>
> Key: SYNCOPE-1384
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1384
> Project: Syncope
> Issue Type: Improvement
> Components: extensions
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Labels: saml
> Fix For: 2.0.11, 2.1.2, 3.0.0
>
>
> At the moment the RequestedAuthnContext is always built as follows:
> {code}
> AuthnContextClassRef authnContextClassRef = new
> AuthnContextClassRefBuilder().buildObject();
>
> authnContextClassRef.setAuthnContextClassRef(AuthnContext.PPT_AUTHN_CTX);
> RequestedAuthnContext requestedAuthnContext = new
> RequestedAuthnContextBuilder().buildObject();
>
> requestedAuthnContext.setComparison(AuthnContextComparisonTypeEnumeration.EXACT);
>
> requestedAuthnContext.getAuthnContextClassRefs().add(authnContextClassRef);
> {code}
> while there might be Service Providers which require it different, or work
> well when RequestedAuthnContext is not provided at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)