In the provisioning process, the proxy host is currently being set to the same host as the API endpoint of the CTI, a holdover from when they used to be the same. To address this issue, we need to instruct the provisioning app to use the correct proxy host.
The simplest solution would be to include this in the /user/me endpoint as with the LK
The consequence is that the proxy certificate is considered invalid because name doesn't match
Example: if proxy host is proxy.example.com and CTI endpoint is cti.example.com, this is the current provisioning query result:
In the provisioning process, the proxy host is currently being set to the same host as the API endpoint of the CTI, a holdover from when they used to be the same. To address this issue, we need to instruct the provisioning app to use the correct proxy host. The simplest solution would be to include this in the /user/me endpoint as with the LK
The consequence is that the proxy certificate is considered invalid because name doesn't match
Example: if proxy host is proxy.example.com and CTI endpoint is cti.example.com, this is the current provisioning query result:
and this is how it should be