On 18/02/2015 22:55, Duquenoy Bruno wrote:
Hi All,
I'm just trying to understand how the mapping is done based on keys.
I don't speak about trivial mapping but on ID mapping.
I'm testing a connector DB et connector LDAP on derby DB and Apache DS.
And I don't understand the column "Internal mapping types" used in the
mapping configuration (Ressource tab).
Then, if "internal mapping types" == UserID, what does it means ? Does
it point on long internal Syncope ID ?
Why does "UserID" and "UserName" are not considered like UserSchema
attributes ?
The wiki page
https://cwiki.apache.org/confluence/display/SYNCOPE/Schema%2C+attributes+and+mapping
doesn't speak about that
Hi Bruno,
the idea behind describing some information as SyncopeUser (or UserTO)
fields rather than schema attributes is to have the possibility to rely
on a (very minimal) set of information associated to user entries (same
applies to roles BTW); consider, in fact, that in a brand new Syncope
installation you don't have nearly any attribute schema but still there
is the need to at least refer to users with their generated id or username.
Coming to resource mapping, the whole idea is associating internal
subjects (user, roles) to external objects (accounts / groups,
respectively); internal subject's information can be something special
(like as UserId, UserName or Password) or something standard (like as
plain, derived or virtual attributes).
Some complimentary information about this can be found at [1], but you
are of course encouraged to improve the wiki page you refer above.
Regards.
[1]
https://cwiki.apache.org/confluence/display/SYNCOPE/External+resources#Externalresources-Schemamapping
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
