personally due to the "headache" and overhead with Atrium SSO, I usually recommend 7.6.03 (without SSO - released Dec 2013) for customers.
If using the 7.7.x versions, Atrium SSO is "https" so you need to allow the installers to take care of the certificate installations. There are a number of discussions surrounding the post installation of the required certificates, and there is a need to understand the fundamentals of Atrium SSO as the way permissions, etc have been handled is different from the earlier versions.
Additionally, there are limitations on Atrium SSO (such as cross domain authentication, HA configuration, etc) that can be a show stopper in an enterprise environment.
To answer your questions, the Dev Studio connects to Atrium SSO via https (as SSO runs only with "https") so it requires the correct certificate to be installed to the correct Java store.
If you are looking to build a Dev or POC environment, then I would recommend 7.6.03 which does not require Atrium SSO which you can setup as "http" communications.
Robin did a great video for installation here:
I have been through the E-Learning Workshop and it was fantastic.
I am currently in the process of removing the 7.7.01 installation and installing 7.6.03. There are just to many issues with the 7.7.01 release around the use of SSL.
Hopefully BMC resolves these in the next release as I do really like the flexibility of Atrium SSO.
we also had lot off issues while configuring the Atrium sso with 7.7.01. but we had successfully resolved all such issues
but for some reason we downgraded to 7.6.X.
Steps by which we resolved our issuess related to ssl on 7.7.01
During SSO 7.7 installation, the installation itself creates a keystore by the name .keystore
in the directory <installation directory>/CDP/tomcat/conf.
We extracted the ssl
certificate from this keystore using below command
#/opt/bmc/java/jdk1.7.0_45/bin/keytool -list -keystore ./keystore (to identify the alias name of the certificate in the keystore)
#keytool -export -keystore examplestore -alias tomcat -file tomcat.crt (to extract the certificate from
the keystore using alias name which is highlighted)
We then imported the extracted certificate in the jvm (cacerts truststore) on AR server
using below command.
#/opt/bmc/java/jdk1.7.0_45/bin/keytool -import -trustcacerts -alias
tomcat -file tomcat.crt -keystore /opt/bmc/java/jdk1.7.0_45/jre/lib/security/cacerts
Did it resolve the issue?