BMC Atrium Single Sign-On is an authentication system that supports many authentication protocols and provides single sign-on and single sign-off for users of BMC Software products. Before you proceed with installing and configuring BMC Atrium Single Sign-On, you must review the system requirements, supported configurations, and compatibility with other BMC products.
You can also verify the system requirements and supported platforms by using the BMC Solution and Product Availability and Compatibility Utility. For more information, see Checking the compatibility matrix for system requirements and supported configurations.
The following topics are provided:
You cannot deploy BMC Atrium Single Sign-On on a Network File System (NFS) system.
Access and permissions
- If you are anonrootruntime user of the BMC Atrium Single Sign-On web container instance, you must be able to write to your own home directory.
- (Microsoft Windows) You must have administrator privileges.
- (UNIX) You can be any user. However, root privileges are required to set up auto-startup of the services.
(LINUX and Oracle Solaris) The $TMP directory must have execute permissions for running the BMC Atrium Single Sign-On installer. You can assign the execute permissions by removing the
noexecattribute from the
/tmpline in the
/etc/fstabfile. For example,
UUID=0aef28b9-3d11-4ab4-a0d4-d53d7b4d3aa4 /tmp ext4 defaults,noexec 1 2
noexecattribute from the line and save the file.
UUID=0aef28b9-3d11-4ab4-a0d4-d53d7b4d3aa4 /tmp ext4 defaults 1 2
For more information see,Installation failure due to insufficient execute permissions.
Supported hardware platforms and operating systems
The BMC Atrium Single Sign-On server supports the following operating systems and platforms. The server supports the listed version and later versions of vendor products.
- The disk space for all operating systems must be 1024 MB.
- If you are installing BMC Atrium Single Sign-On on an external Tomcat server, 2048 MB of RAM is required.
- An additional 7-10 GB of space is recommended for log file growth, depending on the volume of users and products integrating with the BMC Atrium Single Sign-On server.
|32-bit or 64-bit x86 compatible PC|
|Oracle SPARC||Solaris 10 (64-bit only)|
|64-bit x86 compatible PC||Red Hat Enterprise Linux 5, 6, 7 (64-bit only, for Server Editions)|
|Parameter||Small environment||Medium environment||Large environment|
|CPU||2 CPU||4 CPU||4 CPU|
|RAM||4 GB||4 GB||8 GB|
|Storage configuration||100 GB||100 GB||100 GB|
- Microsoft Internet Explorer 10 (support for older versions: 8 and 9)
- Mozilla Firefox 21 (support for older version: 3.5)
- Google Chrome 38
Supported web or application serversThe Tomcat 6.x and later web/application server and servlet engine are supported on all operating systems and platforms supported by BMC as defined in the Supported hardware platforms and operating systems section.
FirewallsThe ports that you selected when you installed the BMC Atrium Single Sign-On server must be accessible from the clients that are authenticated through the server. Configure the firewalls to allow access to the HTTPS port used for authentication, as well as the LDAP and Apache MQ ports in the nodes of a cluster.
BMC Atrium Single Sign-On requires at least Java 6.0 or later.Supportedvendor is:
|Operating system||Vendor||Minimum recommended versions|
|Windows, Solaris, Linux (Red Hat)||Oracle|
Java SE 6 - 1.6.0_28 (32-bit or 64-bit)
Java SE 7 - 1.7.0_17 (32-bit or 64-bit)
Java SE 8 - 1.8.0_66 (32-bit or 64-bit)
Oracle refers to Java 1.6 as “6.0”. For more details, see Java SE Naming and Versions.
Supported platforms for BMC Atrium Single Sign-On agents
Atrium Single Sign-On supports Atrium Single Sign-On agents running on the following operating systems versions or later versions.
Operating Systems - Best performance
- Windows Server 2008, 2012
- Solaris 10
- Red Hat Enterprise Linux 6
Other Operating Systems
- Windows Server 2003
- Red Hat Enterprise Linux 5.5
- HP-UX 11iv2
- Novell SUSE Linux 10
Entropy level requirements
If you are installing BMC Atrium Single Sign-On on Red Hat Enterprise Linux computers, the entropy level on the server must be at least 3000. Otherwise, you might experience installation issues. If an installation or silent installation aborts suddenly, finishes veryquickly,or takes a long time to complete, the computer might be experiencing low entropy issues. To avoid these issues, perform the following tasks:
- Verify the level of entropy in the entropy_avail file at the following location: cat /proc/sys/kernel/random/entropy_avail
If the level of entropy is less than 3000, run the following commands as root user or restart your computer. Running the command is the preferred option as it helps in maintaining the entropy level after installation. If your server has a low entropy level, you should configure your server to run the following commands while starting up your server.rngd
yum install rng-tools echo 'EXTRAOPTIONS="-i -o /dev/random -r /dev/urandom -t 10 -W 2048"' >>/etc/sysconfig/rngd chkconfig rngd on service rngd restart
You must also ensure that the "rngd" process is running.
- LDAPv3, Active Directory
Fully supported Identity Providers:
Active Directory Federation Services (ADFS), Ping Federate, Shiboleth, BMC Atrium SSO, OpenSSO/OpenAM
- Certificates (CAC)
- RSA SecurID Authentication Engine 5.x, 6.x, and 7.x
- BMC Remedy AR System 8.1.x, 7.6.04
- Kerberos v5
Examples of authentication chains
- Kerberos + Kerberos
- LDAP + AR, AR + LDAP, LDAP + LDAP
- AR+ LDAP + LDAP
- Kerberos + AR + LDAP
- SecurID + LDAP
- CAC + LDAP