You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2018/10/15 13:54:00 UTC
[jira] [Resolved] (SYNCOPE-1384) SAML 2.0: Allow to customize
RequestedAuthnContext for a given Service Provider
[ https://issues.apache.org/jira/browse/SYNCOPE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-1384.
---------------------------------------------
Resolution: Fixed
> 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)