You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by Colm O hEigeartaigh <co...@apache.org> on 2016/06/24 11:13:25 UTC
Autocompletion of provisioning rules in 2.0.0
In 1.2.x when creating a resource mapping in the console, you could select
the local attributes from a dropdown box. Also, when using LDAP, it would
display the acceptable values for the external attributes.
In 2.0.0, I couldn't find an obvious way of finding out what the acceptable
values were for user attributes. So for example, I used "groupName" when
mapping groups (instead of "name") and only found out it was wrong when the
groups didn't sync. Finally, I didn't see a list of external attributes as
per 1.2.x. Is this a limitation of 2.0.0 or a bug?
Thanks,
Colm.
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Autocompletion of provisioning rules in 2.0.0
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 24/06/2016 13:37, Francesco Chicchiricc� wrote:
> On 24/06/2016 13:13, Colm O hEigeartaigh wrote:
>> In 1.2.x when creating a resource mapping in the console, you could
>> select the local attributes from a dropdown box. Also, when using
>> LDAP, it would display the acceptable values for the external
>> attributes.
>>
>> In 2.0.0, I couldn't find an obvious way of finding out what the
>> acceptable values were for user attributes. So for example, I used
>> "groupName" when mapping groups (instead of "name") and only found
>> out it was wrong when the groups didn't sync. Finally, I didn't see a
>> list of external attributes as per 1.2.x. Is this a limitation of
>> 2.0.0 or a bug?
>
> Hi Colm,
> SYNCOPE-862 changed the way in which the resource mapping is
> specified, at least for internal attributes.
>
> About the internal attribute specification, I need to document it
> properly in the reference guide, but for the moment you can take as
> reference the content of the info link on the table header (next to
> "Internal attribute" label); the following expressions are valid:
>
> * email (the "email" attribute of the mapping object - being user,
> group or any object)
> * groups[artDirector].icon (the "icon" attribute of the "artDirector"
> group, allowed if the mapping object - user or any object - has
> membership for the "artDirector" group)
> * anyObjects[hp].location (the "location" attribute of the "hp" any
> object, allowed if the mapping object - user or any object - has
> relationship with the "hp" any object)
> * memberships[artDirector].serial (the "serial" attribute of the
> mapping object, related to the membership for the "artDirector" group,
> allowed if the mapping object - user or any object - has membership
> for the "artDirector" group)
>
> About the missing auto-completion with the list of available internal
> and external attributes, this is definitely a bug, please report it.
I went ahead and created
https://issues.apache.org/jira/browse/SYNCOPE-879
Regards.
--
Francesco Chicchiricc�
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/
Re: Autocompletion of provisioning rules in 2.0.0
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 24/06/2016 13:13, Colm O hEigeartaigh wrote:
> In 1.2.x when creating a resource mapping in the console, you could
> select the local attributes from a dropdown box. Also, when using
> LDAP, it would display the acceptable values for the external attributes.
>
> In 2.0.0, I couldn't find an obvious way of finding out what the
> acceptable values were for user attributes. So for example, I used
> "groupName" when mapping groups (instead of "name") and only found out
> it was wrong when the groups didn't sync. Finally, I didn't see a list
> of external attributes as per 1.2.x. Is this a limitation of 2.0.0 or
> a bug?
Hi Colm,
SYNCOPE-862 changed the way in which the resource mapping is specified,
at least for internal attributes.
About the internal attribute specification, I need to document it
properly in the reference guide, but for the moment you can take as
reference the content of the info link on the table header (next to
"Internal attribute" label); the following expressions are valid:
* email (the "email" attribute of the mapping object - being user, group
or any object)
* groups[artDirector].icon (the "icon" attribute of the "artDirector"
group, allowed if the mapping object - user or any object - has
membership for the "artDirector" group)
* anyObjects[hp].location (the "location" attribute of the "hp" any
object, allowed if the mapping object - user or any object - has
relationship with the "hp" any object)
* memberships[artDirector].serial (the "serial" attribute of the mapping
object, related to the membership for the "artDirector" group, allowed
if the mapping object - user or any object - has membership for the
"artDirector" group)
About the missing auto-completion with the list of available internal
and external attributes, this is definitely a bug, please report it.
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/