[
https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162584#comment-17162584
]
ASF subversion and git services commented on SYNCOPE-1583:
----------------------------------------------------------
Commit ecf2975e13a21a32c59a2614e2e2b61379f41832 in syncope's branch
refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=ecf2975 ]
[SYNCOPE-1583] Fix
> For members part of a Dynamic Group, but cannot access group attributes in
> member mapping
> -----------------------------------------------------------------------------------------
>
> Key: SYNCOPE-1583
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1583
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.15, 2.1.6
> Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope
> Reporter: Arun Kumar
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 2.0.16, 2.1.7, 3.0.0
>
>
> We have users U1, U2 ..etc and Other AnyType Classes as well. We created a
> group G1 associated to resource R1 as a dynamic group with rule to
> dynamically make Users/AnyObjects based on a schema attribute on the
> respective type. When we provision members on G1 and then verify membership
> by going to 'members' option on G1, we can see the membership established for
> U1.
>
> But when we have a mapping on a resource R1 with internal attribute -
> _groups[G1].schemaAttribute_ mapped to any external attribute example
> _groupname_, the groupname always comes through as empty. We see the
> membership established in syncope but the group schema attribute value does
> not flow as per mapping.
> The same above mapping works if G1 is a static group and U1 is made a member
> of G1 then we can see the mapping value for _groups[G1].schemaAttribute_
> flow into _groupname_ and thus allow scripts to perform any action based on
> the mapped group attribute.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
