On Wed, Mar 1, 2017 at 2:12 AM, Gayan Gunawardana <[email protected]> wrote:
> > > On Wed, Mar 1, 2017 at 10:58 AM, Indunil Upeksha Rathnayake < > [email protected]> wrote: > >> hi, >> >> As per the SCIM 2.0 Core specification (Refer [1]), there are *resource >> meta attributes such as resourceType, created, lastModified, location and >> version* which are Common Attributes for all the resources. >> As in the specification: "*Each SCIM resource (Users, Groups, etc.) >> includes the following common attributes. With the exception of the >> "ServiceProviderConfig" and "ResourceType" server discovery endpoints and >> their associated resources, these attributes MUST be defined for all >> resources, including any extended resource types.*". >> >> Currently the SCIM meta attributes of a user, saved in the >> "UM_USER_ATTRIBUTES" table with the other user attributes. We are planning >> to move all the SCIM meta attributes to "IDM_USER" table([2]) and make it >> part of User, basically this is to have performance improvements when >> querying for list users(in list users need only to return meta data unless >> client specifically asks for other attributes) etc. >> > @Johann > Is there any other advantage than performance improvement ? > More than looking at it as performance improvement, I would look at it as an inherent part of the user object. There can't exist a user object without filling the metadata attributes. Therefore it is only logical to store it along the global UUID in IDM_USER table. Performance improvement is just a added benefit we get. I didn't look at it from the POV of performance initially. I looked at it and thought it makes sense to have it in IDM_USER even if we forget about performance improvement. > >> But is it correct to move the meta attributes to "IDM_USER" table, since >> those are common attributes which are not directly related to the "User" >> Resource Schema? >> > >> Appreciate your idea on this. >> > +1 I think we need to do same for IDM_GROUP table as well. > >> >> [1] https://tools.ietf.org/html/rfc7643#section-3.1 >> [2] https://github.com/wso2/carbon-identity-mgt/blob/master/ >> feature/org.wso2.carbon.identity.mgt.feature/resources >> /dbscripts/identity-mgt/h2.sql#L21 >> >> Thanks and Regards >> -- >> Indunil Upeksha Rathnayake >> Software Engineer | WSO2 Inc >> Email [email protected] >> Mobile 0772182255 >> > > > > -- > Gayan Gunawardana > Software Engineer; WSO2 Inc.; http://wso2.com/ > Email: [email protected] > Mobile: +94 (71) 8020933 > -- Thanks & Regards, *Johann Dilantha Nallathamby* Technical Lead & Product Lead of WSO2 Identity Server Governance Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+94777776950* Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
