[prev in list] [next in list] [prev in thread] [next in thread] 

List:       forgerock-openidm
Subject:    [OpenIDM] resource type specific attributes __SOMETHING__
From:       laszlo.hordos () forgerock ! com (=?iso-8859-2?Q?L=E1szl=F3_Hord=F3s?=)
Date:       2012-03-30 17:44:50
Message-ID: C383BC85-1CB4-404C-B7AF-2FDBD068DB64 () forgerock ! com
[Download RAW message or body]

Hi Stefan,

Indeed the OpenICF is not well documented but these special names more like a \
functional alias for attributes or object types. OpenICF is a generic connector \
framework and somehow you have to address the object type that represents the "user" \
so you can do if you use the __ACCOUNT__. The connector implementor should recognise \
this type. A good example the LDAP connector where you can create objects and use the \
LDAP object classes. For example if you create an object with type Person or Account \
the connector create an LDAP object with single objectClasses. If you create an \
object with __ACCOUNT__ then the LDAP connector gets the accountObjectClasses \
configuration value will be the objectClasses value. 


The __NAME__ and the __UID__ are more complex You can read Name and Uid but I try to \
explain. In the object model you have to have a value which has some special meaning \
like unique id or a name attribute. For example the ActiveDirectory connector is a \
good example. When you call CreateApiOp a User the object MUST contains a __NAME__ \
attribute and the connector will use that as the primary id. When the user is created \
the AD generates a objectGUID and the operation returns this value. This will be the \
__UID__ so next time when you UpdateApiOp operation is called the OpenICF need this \
value.

These name are "aliases" of functional attributes so the connector implementor knows \
which attribute to use. 


You can find some example for ScriptedSQL connector here.

All the documentation for OpenICF is available at http://openicf.forgerock.org .

I list some urls because as it is now it's very unorganised.
* http://openicf.forgerock.org/faq.html 
* http://openicf.forgerock.org/connector-framework/faq.html 
* http://openicf.forgerock.org/connector-framework-contract/faq.html 
* http://openicf.forgerock.org/development.html 
* http://openicf.forgerock.org/connector-framework-internal/connector_server.html 
* http://openicf.forgerock.org/connector-archetype/ 
* http://openicf.forgerock.org/connector-test-common/usage.html 
* http://openicf.forgerock.org/connector-framework-contract/ 
* http://openicf.forgerock.org/connector-framework-contract/indepth.html 
* http://openicf.forgerock.org/connector-framework-contract/appendix.html 

You can find the original wiki at: \
https://wikis.oracle.com/display/IdentityConnectors/Home

I'm working on some improvements if you take a look into the JIRA you may find some. 
https://bugster.forgerock.org/jira/browse/OPENICF 

Now my priority is a better Maven build process and documentation because I'd like to \
help people who are interested in OpenICF to understand easily the architecture and \
the connector development. If you want to try it out then I suggest to take a look at \
 http://openicf.forgerock.org/connector-archetype 

Regards,
Laszlo

On 29 Mar 2012, at 09:29, blackjack2012 wrote:

> Hello,
> 
> i'm just testing some of the OpenIDM samples from the Installation Guide.
> 
> Since many samples use the __somthing__ objecttypes and attributes, like
> __ACCOUNT__, __UID__ or __NAME__, i wonder if there is any documention or
> other hints on that.
> 
> Especially the scriptedSQL-Connector exmaple would be more understandable
> knowing what those __ things exactly mean.
> 
> The Integration Guide (chapter 5) says : "Attribute names which start and/or
> end with __ are resource type specific attributes used by OpenICF for
> particular purposes, such as __NAME__ as the naming attribute for objects on
> a resource.
> 
> I browsed the OpenICF Homepage on that, but didn't find anything helpfull.
> 
> Any Hints?
> 
> Greetings,
> Stefan
> 
> --
> View this message in context: \
> http://openidm-users.989380.n3.nabble.com/resource-type-specific-attributes-SOMETHING-tp3866957p3866957.html
>  Sent from the OpenIDM Users mailing list archive at Nabble.com.
> _______________________________________________
> OpenIDM mailing list
> OpenIDM at forgerock.org
> https://lists.forgerock.org/mailman/listinfo/openidm

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.forgerock.org/pipermail/openidm/attachments/20120330/b695fa56/attachment.html \



[prev in list] [next in list] [prev in thread] [next in thread]