[Adding [email protected]] I think this was added earlier to store the trusted certificates. Not too sure about how and where it is used. But if it is no more used we better remove them.
Our model now is we import trusted certificates across all tenants to client-truststore.jks. But the downside of this is we cannot have trusted certificates per application. E.g. a set of certificates for SAML SSO and another set for STS. Also currently the client-truststore.jks is not configurable through the management console since we don't save it to registry. One way I have overcome this issue when working on idp-mgt component is by creating a new empty keystore for each tenant being created for my specific application which is idp-mgt. This could easily be done with the tenant creation listeners we have. The advantage of this is we can maintain one truststore per application per tenant, which the best level of separation we can have. On Tue, Sep 24, 2013 at 9:14 AM, Suresh Attanayaka <[email protected]> wrote: > Hi, > > Does anybody know where above keystores are being used and for what? How > they are affected when the product is deployed in production ? > > 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 > -- Thanks & Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+94777776950* Blog - *http://nallaa.wordpress.com*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
