syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (Jira) <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-957) Multiaccount
Date Tue, 03 Dec 2019 12:38:00 GMT

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

Francesco Chicchiriccò commented on SYNCOPE-957:
------------------------------------------------

Also, it is wrong to [read again the whole user|https://github.com/apache/syncope/blob/2_1_X/client/console/src/main/java/org/apache/syncope/client/console/panels/LinkedAccountModalPanel.java#L181]
only to take an updated {{ETag}} value.

> Multiaccount
> ------------
>
>                 Key: SYNCOPE-957
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-957
>             Project: Syncope
>          Issue Type: New Feature
>            Reporter: Francesco Chicchiriccò
>            Assignee: Matteo Alessandroni
>            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)

Mime
View raw message