Re: Syncope user domains

2014-05-30 Thread Marco Di Sabatino Di Diodoro

Il giorno 29/mag/2014, alle ore 17:55, Colm O hEigeartaigh 
cohei...@apache.org ha scritto:

 
 How would one model the concept of user domains in Syncope? Let's say you 
 have two different backends that you synchronize users from + you want to 
 associate all users from resource A with a domain X, and users from resource 
 B with a domain Y.  Is there any easy way of modelling this?

you can use attributes or roles for modeling the concept of user domains. 
Maybe in the future it will be possible to model with realms[1].

 
 The only way I can think of is to have a user domain attribute. Is there a 
 way of specifying a resource user mapping though to map a constant into a 
 user attribute, if say the domain name isn't stored in the backend resource?

You have two options:

1) For each synchronization task you can configure an user template[2]. An user 
template allows you to set a default value for an attribute.
2) Create an Action Class for each synchronization task.

[1] Realm - https://issues.apache.org/jira/browse/SYNCOPE-119
[2] 
https://cwiki.apache.org/confluence/display/SYNCOPE/Synchronize+Active+Directory+with+SQL+database#SynchronizeActiveDirectorywithSQLdatabase-Provideausertemplate


Marco

 
 Colm.
 
 
 -- 
 Colm O hEigeartaigh
 
 Talend Community Coder
 http://coders.talend.com

-- 
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570

Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

Apache Syncope PMC Member
http://people.apache.org/~mdisabatino/



Syncope user domains

2014-05-29 Thread Colm O hEigeartaigh
How would one model the concept of user domains in Syncope? Let's say you
have two different backends that you synchronize users from + you want to
associate all users from resource A with a domain X, and users from
resource B with a domain Y.  Is there any easy way of modelling this?

The only way I can think of is to have a user domain attribute. Is there
a way of specifying a resource user mapping though to map a constant into
a user attribute, if say the domain name isn't stored in the backend
resource?

Colm.


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com