NOTE: Beginning in RLC 6.x, Release Control no longer runs under the Serena Common Tomcat. Instead, it is installed and run using the same JBoss/Tomcat installation that is used by SBM . By importing the certificates into SBM's JRE, you are automatically setting up RLC's JRE.
The users can choose NO and then continue using SBM . ... However, for this to work correctly, the AE host name must also match the "Issued To" name of the certificate in Configurator on the IIS Server view.
SSL cannot be setup in Confiurator if user connects remotely to the server using a "temporary profile". This will cause SBM Configurator in Utility Mode to crash with an exception (the foot-line of SBM Configurator displays "Initializing 'Security' settings...").
1) The first step in configuring SSL is to obtain an SSL certificate . This can either be a self-signed certificate or a certificate obtained through a trusted certificate authority. Note that self-signed certificates will encrypt the user data but will result in a warning message to end users that the certificate may not be valid.
This problem happens in particular configuration, when SSO Federation Server (SSO Login UI) is accessed through 2-way SSL and happens for any SSO enabled web application when user tries to switch to or open second SSO enabled web apps.
