Hi Suresh, Please find the feedback below....
On Thu, Jul 4, 2013 at 12:16 PM, Suresh Attanayaka <[email protected]> wrote: > Hi All, > > Currently our SCIM implementation supports the SCIM Core Schema [1]. > However we are planning to extend the implementation to allow extensions to > those schemas adhering to the SCIM Schema Extension Model [2]. The SCIM > specification itself introduces the SCIM Enterprise User Schema Extension > [3] as an example (please refer the attached image). Our plan is to > implement the extension not limiting only to the Enterprise Extension but > also allowing users to define their own custom attributes including simple, > complex and multivalued attributes. > > Users will be given a configuration file to define their custom attributes > as defined in [2]. Then at the server startup these attributes will be read > and the required objects will be populated. These populated objects will be > added to the User Schema as required. > > From the implementation perspective improvements will be done to the SCIM > Object Decoders (JSONDecoder) to decode the SCIM user objects with the > schema extensions (So we should be able to pass multiple schemas to the > decode methods). > You do not need to change the JSONDecorder... Encoder and Decorder have been written in a generic way to encode/decode SCIM Objects, given their schema. You can extend AbstractSCIMObject in your new SCIM user object and you can either extend the existing resource schema class or implement the resource schema interface in your new resource schema class and utilize the existing methods in JSONDecoder. You may refer the charon design at http://hasini-gunasinghe.blogspot.com/2012/12/wso2-charon-design.html for further details. Other aspects of your design looks fine. Thanks, Hasini. > Then the SCIM Object Validators (ServerSideValidator, ClientSideValidator) > must be extended to validate objects against the extension schemas. An > Extension Schema Popular object will be populating extension schemas with > required attributes. > > [image: Inline image 2] > > > [1]- http://tools.ietf.org/html/draft-ietf-scim-core-schema-01#section-5 > [2]- http://tools.ietf.org/html/draft-ietf-scim-core-schema-01#section-4 > [3]- http://tools.ietf.org/html/draft-ietf-scim-core-schema-01#section-7 > > Please feel free to add your thoughts on this. > > Thanks, > -Suresh > > -- > Suresh Attanayake > Senior Software Engineer; WSO2 Inc. http://wso2.com/ > Blog : http://sureshatt.blogspot.com/ > Web : http://www.ssoarcade.com/ > Facebook : https://www.facebook.com/IdentityWorld > Twitter : https://twitter.com/sureshatt > LinkedIn : http://lk.linkedin.com/in/sureshatt > Mobile : +94755012060 > Mobile : +01-616-617-1172 >
<<image.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
