Hi, On Tue, Apr 18, 2017 at 11:35 AM, Jayanga Dissanayake <jaya...@wso2.com> wrote:
> 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. > IMO we need not have separate jks for each runtime because in a default pack this will be the same for all the runtime and we will be only duplicating it. If the customer wants to have a separate one then they can configure it in the deployment.yaml per runtime and point to a separate jks (for securce vault and SSL, if required) for each runtime. > > Thanks, > Jayanga. > > *Jayanga Dissanayake* > Associate Technical Lead > WSO2 Inc. - http://wso2.com/ > lean . enterprise . middleware > email: jaya...@wso2.com > mobile: +94772207259 <+94%2077%20220%207259> > <http://wso2.com/signature> > > On Tue, Apr 18, 2017 at 9:42 AM, Danesh Kuruppu <dan...@wso2.com> 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: dan...@wso2.com >> Web: WSO2 Inc <https://wso2.com/signature> >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > Regards, Nira -- *Niranjan Karunanandham* Associate Technical Lead - WSO2 Inc. WSO2 Inc.: http://www.wso2.com
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
