This article applies to the following ScreenBeam products:
The team at ScreenBeam has become aware of an important limitation in CMS Enterprise 184.108.40.206, this limitation does not pose a functionality or security risk, but does impact user experience. If after upgrading to CMS Enterprise 220.127.116.11 you are stuck on the Identity Server login page please review the information below.
When installing CMS Enterprise 18.104.22.168 as a new installation or as an upgrade from a previous installation the administrator will be prompted to enter the IP address or FQDN of the server, by default the installer will populate the server's IP address. In this version, only the IP address or FQDN specified on this page can be used to log in to CMS Enterprise through a web browser.
In previous versions of CMS Enterprise, IP address, FQDN, and localhost (when on the server) could all be used to log in and manage ScreenBeams. This is being treated as a known limitation and will be addressed in a future CMS Enterprise release.
This configuration has no impact on ScreenBeam receivers, this limitation only impacts the admin user experience.
Note that due to the nature of how the FireFox web browser stores security exceptions you will need to create additional security exceptions for each port used by CMS Enterprise (8888, 8889, 8890). To create the security exception click on the Application Menu in FireFox and choose Settings, go to the Privacy & Security tab and scroll down to the Security section, under Certificates, click View Certificates.
In the Certificate Manager window, go to the Servers tab and click Add Exception... then in the location field type the IP address of FQDN of your CMS Enterprise server and add the port extensions for 8888, 8889, and 8890 then press Confirm Security Exception.
Once completed, you should have 3 Servers listed with Security Exceptions, press Ok.
Google Chrome and Microsoft Edge store security exceptions for all ports on a particular page, so no additional configuration is required.