We have the transport file as well as the keystore file for HTTPS. It is possible to embed the transport file but then we can't edit it. However, embedding the keystore file in the jar is not practical because the developer will not have access to the production keystore file while doing day to day development.
On Wed, Feb 24, 2016 at 1:39 PM, Asanka Vithanage <asan...@wso2.com> wrote: > Hi, > > In this case cant we implement same approach as OSGI for fat jar mode. > Basically at Micro service development stage we define the config file in a > default path and bundle it inside Jar file. Then execution level read the > config and define HTTPS transport accordingly. > > On Wed, Feb 24, 2016 at 12:38 PM, Afkham Azeez <az...@wso2.com> wrote: > >> It is not practical to allow hardcoding of HTTP related parameters such >> as keystore password etc. so the best approach is passing in the config >> file. For OSGi mode, the Netty transport bundle will look for the transport >> config file in the default path and load it if found. >> >> On Wed, Feb 24, 2016 at 12:28 PM, Asanka Vithanage <asan...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> Currently if we need to enable HTTPS for micro service [in fat jar mode] >>> we should define it on a netty-transports.yml file and run the jar file >>> with define configuration. check the doc [1]. >>> >>> I believe we should provide both HTTP and HTTPS inbuilt support in fat >>> jar mode.Since current way supporting HTTPS is not much user friendly. Do >>> we have an any technical limitation in providing this support? WDYT? >>> >>> Further we don't have any documentation or sample which explains how to >>> enable HTTPS on osgi mode as well. >>> >>> [1] >>> https://docs.wso2.com/display/MSF4J100/Invoking+Your+Microservice+via+HTTPS >>> >>> -- >>> Asanka Vithanage >>> Senior Software Engineer -QA >>> Mobile: +94 0716286708 >>> Email: asan...@wso2.com >>> WSO2 Inc. www.wso2.com >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>* >> *email: **az...@wso2.com* <az...@wso2.com> >> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: * >> *http://blog.afkham.org* <http://blog.afkham.org> >> *twitter: **http://twitter.com/afkham_azeez* >> <http://twitter.com/afkham_azeez> >> *linked-in: **http://lk.linkedin.com/in/afkhamazeez >> <http://lk.linkedin.com/in/afkhamazeez>* >> >> *Lean . Enterprise . Middleware* >> > > > > -- > Asanka Vithanage > Senior Software Engineer -QA > Mobile: +94 0716286708 > Email: asan...@wso2.com > WSO2 Inc. www.wso2.com > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **az...@wso2.com* <az...@wso2.com> * cell: +94 77 3320919blog: **http://blog.afkham.org* <http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez* <http://twitter.com/afkham_azeez> *linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
