On Mon, Oct 16, 2017 at 1:28 AM, Johann Nallathamby <[email protected]> wrote:
> IAM Devs, > > I think for all the well know Identity Providers (including social > authentication sites) we have the practice of defining a claim dialect in > claim management to do mapping easily without having to duplicate for each > IdP in each tenant. For the OOTB connectors we may be shipping these > mappings in claim-config.xml. But how are we expecting the users to do this > for the connectors in the store? Have they got to do it manually by looking > at the documentation for the super tenant and each tenant created so far? > > How about if we can do this one time setup task in the connector itself > for super tenant and all existing tenants? Basically if we can define the > new dialect in claim-config.xml and restart the server, when the > getClaimDialectURI() method of each connector is invoked we can check for > the existence of the dialect in the super tenant and each of the tenants > created so far and execute a logic to read and store the new dialect once > after startup. This will cause the first request to the connector to be > slower. I was thinking of a init() method that may be called on server > startup but I don't think we have one for ApplicationAuthenticator API. > In fact we can even do this in each of the connector active() method also right? This will make sure the first request isn't slowing down. > > This logic can be written in the common utility bundle of all the > extensions and shared across the connectors. > > Thoughts? > > Regards, > Johann. > > -- > > *Johann Dilantha Nallathamby* > Senior Lead Solutions Engineer > WSO2, Inc. > lean.enterprise.middleware > > Mobile - *+94777776950* > Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>* > -- Thanks & Regards, *Johann Dilantha Nallathamby* Senior Lead Solutions Engineer 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
