Hi Chanuka, When we create new dialect , are they any possibility to select user store ? Because user store variable is available with the current API and with that we can have user store specific claims.
*Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * <http://www.apache.org/>* *email: **[email protected]* <[email protected]>* cell: +94 71 5186770 * *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* *harshathirimannlinked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>* *Lean . Enterprise . Middleware* On Mon, Apr 27, 2015 at 6:21 PM, Chanuka Dissanayake <[email protected]> wrote: > Hi, > > These tables will be effected with the $subject. UM_DIALECT table [1] will > contain the Dialect uri and the Tenant ID, which is not going to be change. > In IM_CLAIM table [2] only the information of the WSO2 claims will be > stored. UM_MAPPED_ATTRIBUTE and UM_MAPPED_ATTRIBUTE_DOMAIN attributes will > be moved to another table [3] (UM_MAPPED_ATTRIBUTES) with the foreign key > (UM_CLAIM_ID) of UM_CLAIM table [2] which contains the Mapped Attributes of > the WSO2 claims. UM_OTHER_CLAIM table [4] will contains the foreign key > (UM_DIALECT_ID) and foreign key (UM_CLAIM_ID) from the table [1] and [2] > respectively. > > Note: Table names are subject to change. > > [1] UM_DIALECT > > UM_ID > > UM_DIALECT_URI > > UM_TENANT_ID > > > > > [2] UM_CLAIM > > UM_ID > > UM_DIALECT_ID > > UM_CLAIM_URI > > --- > > > > > > [3] UM_MAPPED_ATTRIBUTES > > UM_ID > > UM_CLAIM_ID > > UM_MAPPED_ATTRIBUTE > > UM_MAPPED_ATTRIBUTE_DOMAIN > > > > > [4] UM_OTHER_CLAIMS > > UM_ID > > UM_DIALECT_ID > > UM_CLAIM_ID > > OTHER_CLAIM_URI > > > > > > > Thanks, > Chanuka. > > On Fri, Apr 24, 2015 at 10:19 AM, Chanuka Dissanayake <[email protected]> > wrote: > >> Hi Harsha, >> >> If the WSO2 claim has the ‘Required’ field as ‘true’(checked), then it’ll >> be the value for that claim and other dialect will have the same value for >> ‘Required’ field (Cannot change, will be disabled from UI). If that value >> is ‘false’ in the WSO2 claim, then other dialects can change the value as >> desire. For the ‘Read only’ field It’ll be the same scenario. Other fields >> will override the WSO2 claim values, which is configurable (Display Name, >> Description, Display Order, Supported by Default). Yes, Identity >> Provider claim configurations will also be change accordingly. >> Regards, >> Chanuka. >> >> On Fri, Apr 24, 2015 at 8:29 AM, Harsha Thirimanna - WSO2, Inc. < >> [email protected]> wrote: >> >>> How about the Identity Provider claim configurations ? >>> >>> >>> *Harsha Thirimanna* >>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>> * <http://www.apache.org/>* >>> *email: **[email protected]* <[email protected]>* cell: +94 71 5186770 * >>> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* >>> *harshathirimannlinked-in: **http: >>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>* >>> >>> *Lean . Enterprise . Middleware* >>> >>> >>> On Fri, Apr 24, 2015 at 8:17 AM, Harsha Thirimanna - WSO2, Inc. < >>> [email protected]> wrote: >>> >>>> >>>> On Fri, Apr 24, 2015 at 8:00 AM, Harsha Thirimanna - WSO2, Inc. < >>>> [email protected]> wrote: >>>> >>>>> On Thu, Apr 23, 2015 at 7:51 PM, Chanuka Dissanayake <[email protected] >>>>> > wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Followings are the improvements to the IS claim management. RM [1]. >>>>>> >>>>>> >>>>>> - Remove attribute/claim mapping for each dialect. Only WSO2 >>>>>> dialect will have the attribute mapping - rest will refer to WSO2 >>>>>> claim >>>>>> dialect >>>>>> >>>>>> When adding a new claim “Mapped Attribute(s)” row will be replaced >>>>>> with a dropdown "Local Claim”, which contains the WSO2 claims. In this >>>>>> scenario IMO, It’s better to keep other fields as it is ( >>>>>> >>>>>> Description, Claim Uri, Regular Expression, Display Order, Supported >>>>>> by Default and Required, Read-only), because it can vary according to the >>>>>> dialect. [Image 1] >>>>>> >>>>>> *These Description, Claim Uri, etc are some meta data about the >>>>> attribute. How about if this meta data also as configurable. Then any one >>>>> can add meta data field to the claim attribute.* >>>>> >>>> >>>> >>>> *And , there are two category we can define from meta data. One is as >>>> meta data(static) and other one is for validaters. Then some day we can add >>>> some handler to write custom validators(custom logic) for the claims. WDYT >>>> ? * >>>> >>>> >>>> >>>>> >>>>> >>>> >>>>> >>>>>> >>>>>> - Service provider should be able to define its own claim dialect >>>>>> >>>>>> When adding/editing a Service Provider, Under the Claim Configuration >>>>>> there will be an option as “Add New Claim Dialect” ('Define Custom Claim >>>>>> Dialect’ will be removed ). When adding a new Claim Dialect, It will be >>>>>> same as first scenario. Defined claim dialects under Service Providers >>>>>> will >>>>>> separately listed down(viewed) under claim management. [Image 2] >>>>>> >>>>>> >>>>>> - Improve claim management UI for user store based claims. >>>>>> >>>>>> Previously 'Mapped Attribute(s)' are typed and separated from >>>>>> semicolons. [Image 3] >>>>>> >>>>>> Improvement: Attribute Name can type inside the textbox and >>>>>> appropriate User Store can be selected from the dropdown, and delete >>>>>> button >>>>>> to remove the attribute. For multiple Mapped Attributes there will be >>>>>> multiple rows. [Image 4] >>>>>> >>>>>> [1] https://redmine.wso2.com/issues/3903 >>>>>> >>>>>> Thanks & Regards, >>>>>> Chanuka. >>>>>> -- >>>>>> Chanuka Dissanayake >>>>>> *Software Engineer | **WSO2 Inc.*; http://wso2.com >>>>>> >>>>>> Mobile: +94 71 33 63 596 >>>>>> Email: [email protected] >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Chanuka Dissanayake >> *Software Engineer | **WSO2 Inc.*; http://wso2.com >> >> Mobile: +94 71 33 63 596 >> Email: [email protected] >> > > > > -- > Chanuka Dissanayake > *Software Engineer | **WSO2 Inc.*; http://wso2.com > > Mobile: +94 71 33 63 596 > Email: [email protected] > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
