spooky_tooth
Vendor
Happy New Year everyone!
In the SBC I have a reverse proxy for AADS setup on port 8443 and PPM on port 443 going to SM. PPM and auto config from AADS are working fine but I can't get the "Contact Service" to work. I notice when I browse to the public certed B1 at " I can see that the REST API links for GET, POST, etc. point to the actual FQDN of the AADS server and not to the B1 FQDN. As the AADS FQDN is not resolvable from the outside world none of the links work when you click them. If I put a host entry in the PC running Windows client I can click on any of the links from a web browser test and the contact service on the client starts to work also. Does anyone know if there is a way to re-write the FQDN in the links in the REST API to the FQDN of the B1? I have so far tried messing with the reverse proxy listen domain and re-writing the URL in the SBC to no avail.
Thank you!
In the SBC I have a reverse proxy for AADS setup on port 8443 and PPM on port 443 going to SM. PPM and auto config from AADS are working fine but I can't get the "Contact Service" to work. I notice when I browse to the public certed B1 at " I can see that the REST API links for GET, POST, etc. point to the actual FQDN of the AADS server and not to the B1 FQDN. As the AADS FQDN is not resolvable from the outside world none of the links work when you click them. If I put a host entry in the PC running Windows client I can click on any of the links from a web browser test and the contact service on the client starts to work also. Does anyone know if there is a way to re-write the FQDN in the links in the REST API to the FQDN of the B1? I have so far tried messing with the reverse proxy listen domain and re-writing the URL in the SBC to no avail.
Thank you!