What about the port? On Monday, November 23, 2015, Chamara Ariyarathne <[email protected]> wrote:
> So Geeth, my argument is even if there is a url re-write in the load > balancer, the carbon.xml HostName and MgtHostName value should be the > domain name which is exposed to outside world, > > hence in your example: emm.wso2.com. > > Do you have a counter argument for this? > > On Mon, Nov 23, 2015 at 8:03 PM, Geeth Munasinghe <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Hi Chamara >> >> For the first issue, as you and me had many offline discussions about it, >> let me explain the reason again, why we moved the LB host name and LB port >> to be taken from a different file (cdm-config.xml). This was required when >> we send email to users to get their devices enrolled, we need to get the LB >> host and port. >> >> When we configure the EMM servers, they will be in private network IPs. >> And those EMM servers will be exposed to the out side through a load >> balancer which will be on public IP. Normally load balancer will run on >> default http and https ports which are either 80 or 443. But EMM servers >> could run on any port (default 9443 and 9763). So when a load balancer >> receives a request to either 80 or 443 ports, it will redirect them to EMM >> server 9443 / 9763 ports. >> >> Another thing is load balancer could rewrite the urls, for example if the >> load balancer host name and port is https://emm.wso2.com:443, then in LB >> it can rewrite the urls to https://worker.mdm.com:9443. >> >> So AFAIK there is no configuration in carbon.xml where we can get the LB >> host name and port. >> >> And for the second issue, It is a bug which we will fix in next alpha >> release. But to fix this, I think the same rule applies. It cannot be taken >> from carbon.xml because mgt host name does give any impression about the >> load balancer url. So it should be taken from cdm-config.xml. >> >> Thanks >> Geeth >> >> >> *G. K. S. Munasinghe* >> *Senior Software Engineer,* >> *WSO2, Inc. http://wso2.com <http://wso2.com/> * >> *lean.enterprise.middleware.* >> >> email: [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');> >> phone:(+94) 777911226 >> >> On Mon, Nov 23, 2015 at 6:51 PM, Chamara Ariyarathne <[email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >> >>> We have a major design culprit with this situation now with the hostname >>> not getting picked up from carbon.xml. First reported jira is this >>> https://wso2.org/jira/browse/EMM-900 >>> >>> Today we found out that even when the Host Names are configured in the >>> carbonl.xml to be server's identified domain name, the QR code which is >>> generated while device registration, uses the host ip address which is >>> picked up from nowhere. >>> https://wso2.org/jira/browse/EMM-987 >>> >>> This issue will break the clustering scenarios where we need to define >>> host names in carbon.xml but EMM not picking them up properly. >>> >>> On Tue, Nov 17, 2015 at 3:18 PM, Chamara Ariyarathne <[email protected] >>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >>> >>>> Hi Azeez, >>>> >>>> Agree with that. However the precedence should be to use the HostName >>>> value in the carbon.xml which is ultimately the deployment's exposed host >>>> name, hence the constructed url in the email would be the correct access >>>> url from outside. >>>> >>>> My argument is, this url shouldn't be kept in some other configuration >>>> file repeatedly. >>>> >>>> Thanks. >>>> >>>> On Wed, Nov 11, 2015 at 7:04 PM, Afkham Azeez <[email protected] >>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >>>> >>>>> This is for information purposes only. The mail says the URL we send >>>>> to the users in the email contains local host. May be you can get the IP >>>>> address/host from the incoming request and use that. >>>>> >>>>> On Wed, Nov 11, 2015 at 3:59 AM, Geeth Munasinghe <[email protected] >>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >>>>> >>>>>> Hi Azeez, >>>>>> >>>>>> In case of URL rewrite by LB, can we handle that by the proxy >>>>>> settings on catalina-server.xml ? >>>>>> >>>>>> Thanks >>>>>> Geeth >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> *G. K. S. Munasinghe* >>>>>> *Senior Software Engineer,* >>>>>> *WSO2, Inc. http://wso2.com <http://wso2.com/> * >>>>>> *lean.enterprise.middleware.* >>>>>> >>>>>> email: [email protected] >>>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');> >>>>>> phone:(+94) 777911226 >>>>>> >>>>>> On Wed, Nov 11, 2015 at 2:10 PM, Afkham Azeez <[email protected] >>>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >>>>>> >>>>>>> proxy host name >>>>>>> >>>>>>> On Wed, Nov 11, 2015 at 12:28 AM, Chamara Ariyarathne < >>>>>>> [email protected] >>>>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> When a new user is added to EMM, the user will be notified with an >>>>>>>> email to subscribe a device to MDM domain. The email contains the >>>>>>>> server >>>>>>>> url to be accessed from the device. >>>>>>>> >>>>>>>> https://localhost:9443/mdm/enrollment >>>>>>>> >>>>>>>> In a usual deployment when a EMM cluster is fronted by a LB, this >>>>>>>> url should be changed to the particular gateway host of the >>>>>>>> deployment. Now >>>>>>>> a doubt arose whether to create this url by taking the value in >>>>>>>> HostName >>>>>>>> element in carbon.xml or somewhere else. >>>>>>>> >>>>>>>> So the real doubt here is what is the correct way to configure the >>>>>>>> HostName attribute in the carbon.xml in a carbon server. Is it going >>>>>>>> to be >>>>>>>> the LB host's url which the deployment is exposed with or is it some >>>>>>>> local >>>>>>>> host name internal to the deployment? >>>>>>>> >>>>>>>> -- >>>>>>>> *Chamara Ariyarathne* >>>>>>>> Associate Technical Lead - QA >>>>>>>> WSO2 Inc; http://www.wso2.com/ >>>>>>>> Mobile; *+94772786766 <%2B94772786766>* >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Afkham Azeez* >>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>> * <http://www.apache.org/>* >>>>>>> *email: **[email protected]* >>>>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');> >>>>>>> * 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* >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>> * <http://www.apache.org/>* >>>>> *email: **[email protected]* >>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');> >>>>> * 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* >>>>> >>>> >>>> >>>> >>>> -- >>>> *Chamara Ariyarathne* >>>> Associate Technical Lead - QA >>>> WSO2 Inc; http://www.wso2.com/ >>>> Mobile; *+94772786766 <%2B94772786766>* >>>> >>> >>> >>> >>> -- >>> *Chamara Ariyarathne* >>> Associate Technical Lead - QA >>> WSO2 Inc; http://www.wso2.com/ >>> Mobile; *+94772786766 <%2B94772786766>* >>> >> >> > > > -- > *Chamara Ariyarathne* > Associate Technical Lead - QA > WSO2 Inc; http://www.wso2.com/ > Mobile; *+94772786766* > -- *G. K. S. Munasinghe* *Senior Software Engineer,* *WSO2, Inc. http://wso2.com <http://wso2.com/> * *lean.enterprise.middleware.* email: [email protected] phone:(+94) 777911226
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
