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

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

Commit 1cf0d2a02873926d6a2b41f1cb11d2cc0aa5ab83 in syncope's branch 
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=1cf0d2a ]

[SYNCOPE-1146][SYNCOPE-1147] Now it possible to configure an IdP to create 
unmatching users / update matching users; the defined mapping, alongside with 
user template and SAML2IdPActions implementations are taken into account to 
provide the actual user data


> On-the-fly creation of unmatched users logging via SAML 2.0
> -----------------------------------------------------------
>
>                 Key: SYNCOPE-1146
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1146
>             Project: Syncope
>          Issue Type: Improvement
>          Components: extensions
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>              Labels: saml
>             Fix For: 2.0.5, 2.1.0
>
>
> As per the current implementation, when logging into the Admin Console via 
> SAML 2.0, an internal user matching the configured attribute of the 
> Authentication Assertion is looked up.
> If not found, an error is raised.
> Things could be configured, however, to create on-the-fly an internal user 
> with the attributes provided by the Authentication Assertion, and to let them 
> log in.



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

Reply via email to