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

List:       forgerock-openidm
Subject:    [OpenIDM] custom OpenIDM connector -- accept JSON with SCIM-like nested attributes
From:       keremkacel () gmail ! com (keremkacel)
Date:       2012-11-20 17:46:39
Message-ID: 83DE5C4B-4FEC-40FE-8161-053D5563FCC4 () gmail ! com
[Download RAW message or body]

Thank you for the implementation details Laszlo.

Kerem

Sent from my iPhone

On Nov 19, 2012, at 3:48, L?szl? Hord?s [via OpenIDM Users] \
<ml-node+s989380n4025193h11 at n3.nabble.com> wrote:

> Hi Kerem,
> 
> The OpenICF framework does not supports the nested attributes. It's a simplified \
> and generalised framework and the design was heavily  influenced by the Sun IDM and \
> LDAP. It only supports attribute and collection values like the LDAP. Some of the \
> attribute is single valued but down at API level it's  
> Map<String, List<Object>> and the list may contains only one of the following \
> types: String
> long
> Long
> char
> Character
> double
> Double
> float
> Float
> int
> Integer
> boolean
> Boolean
> byte[]
> BigDecimal
> BigInteger
> GuardedByteArray
> GuardedString
> If you want to support complex types then you need to serialise it and then the \
> connector can de-serialise but the framework nor OpenIDM does it. 
> I hope it answers your question.
> 
> Regards,
> Laszlo
> 
> 
> On 15 Nov 2012, at 15:46, keremkacel wrote:
> 
> > Thank you for the quick response Gael.
> > 
> > I tried two different configs -- and both fail.
> > 
> > 1)
> > https://www.dropbox.com/s/og913zdx9keao4q/provisioner.openicf-ice1.txt
> > In this one I defined name as an object, and created a properties node and
> > nested the child attributes (familyName, givenName etc) under that.
> > 
> > 2)
> > https://www.dropbox.com/s/ndjkp4wo0fuvttt/provisioner.openicf-ice2.txt
> > In this one I defined name as a parent objectType (just like account) and
> > nested the child attributes under that -- and then listed name as an
> > attribute (of type "name") among the attributes of the account.
> > 
> > To answer your question, I do not necessarily need to pass "name" as an
> > attribute itself, however I need to be able to access the child attributes
> > of name.
> > 
> > If I just list them flat in the config (as if they were direct children of
> > account), will that work?
> > If so, how would I handle similarly-named child attributes of different
> > nodes such as:
> > 
> > "name": {
> > "familyName": "Jensen",
> > "givenName": "Barbara",
> > "middleName": "Jane",
> > },
> > "supervisor": {
> > "familyName": "Smith",
> > "givenName": "John",
> > "middleName": "Jack",
> > }
> > 
> > 
> > Thank you,
> > 
> > Kerem
> > 
> > 
> > 
> > --
> > View this message in context: \
> > http://openidm-users.989380.n3.nabble.com/OpenIDM-custom-OpenIDM-connector-accept-JSON-with-SCIM-like-nested-attributes-tp4025180p4025183.html
> >  Sent from the OpenIDM Users mailing list archive at Nabble.com.
> > _______________________________________________
> > OpenIDM mailing list
> > [hidden email]
> > https://lists.forgerock.org/mailman/listinfo/openidm
> 
> 
> _______________________________________________ 
> OpenIDM mailing list 
> [hidden email] 
> https://lists.forgerock.org/mailman/listinfo/openidm
> 
> 
> If you reply to this email, your message will be added to the discussion below:
> http://openidm-users.989380.n3.nabble.com/OpenIDM-custom-OpenIDM-connector-accept-JSON-with-SCIM-like-nested-attributes-tp4025180p4025193.html
>  To unsubscribe from [OpenIDM] custom OpenIDM connector -- accept JSON with \
> SCIM-like nested attributes, click here. NAML




--
View this message in context: \
http://openidm-users.989380.n3.nabble.com/OpenIDM-custom-OpenIDM-connector-accept-JSON-with-SCIM-like-nested-attributes-tp4025180p4025196.html
 Sent from the OpenIDM Users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.forgerock.org/pipermail/openidm/attachments/20121120/a45aafa6/attachment.html \



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