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 2019/10/02 10:46:01 UTC

[jira] [Commented] (SYNCOPE-957) Multiaccount

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

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

Commit bb0100731b8655ceb8e0cab3f9855b6c1a6f2754 in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=bb01007 ]

[SYNCOPE-957] Push implemented


> Multiaccount
> ------------
>
>                 Key: SYNCOPE-957
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-957
>             Project: Syncope
>          Issue Type: New Feature
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 2.1.6, 3.0.0
>
>
> Users, as groups and any objects, can be mapped to external resources and pull, push or propagation might result in associating them to accounts there.
> So far, there have always been a 1-to-1 correspondence between Syncope users and external accounts, given a certain mapping for an external resource.
> There are use cases, however, when this could be limiting: in particular, the existence of "service accounts" which can be defined on LDAP or Active Directory. In such cases, there could be more accounts mapping to a Syncope user.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)