Hi Danesh, +1 for the suggested approach. It will allow keeping the /wso2 directory untouched by the users.
And having different key stores for different runtimes is a valid use-case. Hence +1 for having secvault and transport keys stores with different names for each runtime in the /resources/security directory. Thanks, Jayanga. *Jayanga Dissanayake* Associate Technical Lead WSO2 Inc. - http://wso2.com/ lean . enterprise . middleware email: [email protected] mobile: +94772207259 <http://wso2.com/signature> On Tue, Apr 18, 2017 at 9:42 AM, Danesh Kuruppu <[email protected]> wrote: > Hi Thusitha, > > >> Shouldn't we move resource dir to <runtime_home> as well? AFAIU each >> runtime can have their own JKS. WDYT? >> > > Current idea is to have common jks files(one jks for securevault and one > for the transport) for all runtime in the distribution. Since this also can > change by the end user, we need to move out from the wso2 directory. If we > need to keep them per runtime, we can keep them in the same location with > different name and refer it from the runtime configuration file. > > WDYT? > > Thanks > -- > > *Danesh Kuruppu* > Senior Software Engineer | WSO2 > > Email: [email protected] > Web: WSO2 Inc <https://wso2.com/signature> > > > _______________________________________________ > 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
