cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Change NAM console public URL

timothy_braeckm
Visitor

You can set the NAM console public URL with the installation according the topic NAM Console public connectivity of the installation document https://www.dynatrace.com/support/doc/nam/installa.... I cannot find change the NAM console public URL after the installation. Does anybody know how to change the public URL of NAM Console after the installation?


5 REPLIES 5

Joanna_Kozlowsk
Newcomer

To change NAM Console public URL, please open Console -> Authentication -> SSO and federation page.

Change the URL there to desired one and click Save button.

In 18.0.0 the option was available in installer, in Add/remove programs, but it was removed on purpose.

Regards,

Joanna


Does the change here propagate to the NAM Servers? via a restart?

thanks


timothy_braeckm
Visitor

Unfortunately it changes only the redirect of URL when logging on or off. It doens't change the url of the NAM console.


Joanna_Kozlowsk
Newcomer

I am not sure if I understand you correctly then.

According to changing the private Console address settings (Console installer in Add/remove programs), you are only able to change the ports and enabled connection protocols (refer to: https://www.dynatrace.com/support/doc/nam/installation/install-rum-console/?_ga=2.205875795.1540889823.1546937283-1498365667.1508150619#144nam-console-private-connectivity)

However if you mean updating the private URL to Console on NAM Server, I refer you to NAM Server installer (Add/remove programs):

https://www.dynatrace.com/support/doc/nam/installation/install-cas-or-ads/#129nam-console-connection


timothy_braeckm
Visitor

The NAM Server and NAM console are installed on same server but NAM Console is accessible with a port, example:

First I installed SSL certificate on NAM Server Frontend. The keystore of NAM Server Frontend had 3 certificates. I copied the keystore because the same URL and also adjusted the certificate with the documentation. The problem was NAM Console couldn't handle a keystore with 3 certificates. NAM Console needs only 1 certificate on keystore, otherwise it wont work properly.