Remedy Single Sign-On (Remedy SSO) is an authentication system that supports authentication protocols and provides single sign-on and single sign-off for users of BMC Remedy products. The following list contains hardware and software requirements to install and configure Remedy SSO.
To plan your deployment or upgrade, you must first review the BMC Solution and Product Availability Utility (SPAC) for Remedy Single Sign-On (Remedy SSO) to understand the supported environments, required third party software, and compatibility with other BMC products and integrations.
To access the compatibility matrix
Navigate to .
To access the product compatibility information on the Customer Support website, you must have a Support ID.
- Click BMC PRODUCT AND VERSION.
- In the Product Name field, select a product name; for example, Remedy AR System Server.
The system requirements for BMC Remedy AR System also apply to the BMC Remedy ITSM Suite, BMC Remedy Service Level Management, BMC Remedy Service Request Management, BMC Remedy Approval Server, BMC Remedy Email Engine, BMC Remedy Distributed Server Option (DSO), BMC Remedy Encryption Performance Security, and BMC Remedy Encryption Premium Security.
- In the Product Version field, select a version number.
Review the following system configuration information to ensure your environment aligns with the following requirements:
- Operating systems and platform support
- Database support
- Third party prerequisites, such as Java requirements
- Third party product compatibilities, such as the web or application server, servlet engine, and browser support
- Screen reader support
- Language offerings
Compatible BMC product versions
Access and permissions
- If you are a non-root runtime user of the Remedy SSO web container instance, you must be able to write to your own home directory.
- (Microsoft Windows) You must have administrator privileges.
(LINUX ) The $TMP directory must have execute permissions for running the Remedy SSO 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
Ensure that you have database user credentials with permissions to create tables and read/write data to them or you have admin credentials to create such a user during installation. Script examples for creating such permissions are as follows.
If Remedy SSO is configured to use the existing Remedy AR System database instance, you must not use the AR System database name for Remedy SSO. Use a new database name for Remedy SSO to prevent the table name conflict for the Configuration table. If you are using Oracle, create a new schema for Remedy SSO before running the BMC Remedy installer. At the time of installation select the new database.
CREATE DATABASE <database> CREATE LOGIN user WITH PASSWORD = <pwd>, DEFAULT_DATABASE = <database> USE <database> CREATE USER <user> FOR LOGIN <user> WITH DEFAULT_SCHEMA = dbo EXEC SP_ADDROLEMEMBER DB_OWNER, <user>
CREATE USER <user> IDENTIFIED BY <pwd> GRANT CONNECT, RESOURCE TO user IDENTIFIED BY <pwd> If you have Oracle 12c on the system, you must run the following script to provide a quota for a user on the tablespace. ALTER USER <user> quota unlimited on <tablespace name>
CREATE DATABASE "<database>"; CREATE ROLE "<user>" WITH LOGIN PASSWORD '<pwd>'; GRANT ALL PRIVILEGES ON DATABASE "<database>" TO "<user>"; GRANT ALL ON ALL TABLES IN SCHEMA public TO "<user>";
- Ensure that you have the operating system user account to:
- Install and run Remedy SSO server with permissions to run the installer
- Write Remedy SSO binaries to the destination directory and execute them
- Write config files and Remedy SSO plugin and agent jar files to the directories of Remedy AR System, Remedy Mid Tier, BMC Smart IT or BMC Digital Workplace, and BMC Analytics for BSM.
Supported hardware platforms and operating systems
The Remedy SSO server is supported on the following operating systems and platforms and their later versions.
|64-bit x86 compatible PC||
- The minimum available disk space on all operating systems must be 1024 MB or higher.
- The Tomcat server on which you install Remedy SSO must have 2048 MB of RAM.
- An additional 7-10 GB of space is recommended for log file growth, depending on the volume of users and products integrating with the Remedy SSO server.
- Microsoft Internet Explorer 10
- Mozilla Firefox
- Google Chrome
Supported web or application servers
The Tomcat 7 and 8 web/application server and servlet engine are supported on all operating systems and platforms supported by BMC and as defined in the supported hardware platforms and operating systems section.
For more information about security settings, see Security planning.
- MS SQL 2008 and above
- Should be accessible through TCP (not named pipes)
- Should be configured to use SQL Server authentication (not integrated Windows authentication)
- Remedy SSO supports MS SQL Server 'Always On configuration' feature, a DB cluster setup, which is the same for BMC Remedy AR System (Starting from version 9.1.01)
- Oracle 11gR2 and Oracle 12c
- PostgreSQL (Starting from version 9.1.02)
Remedy SSO can operate on HTTP or HTTPS ports configured in the user's web server. These ports should be accessible from the machines where integrated products such as BMC Remedy Mid Tier, BMC Digital Workplace, and BMC Analytics are installed.
Remedy SSO uses MS SQL and Oracle database and hence the used ports should be accessible from Remedy SSO nodes.
Remedy SSO requires Java version 7.0 or above. The supported vendor is:
Java SE 7
- JRE must be installed before you install Remedy SSO as the Remedy SSO installer does not include the bundled JRE.
- Oracle refers to Java 1.7 as “7.0”. For more details, see Java SE Naming and Versions.
- Oracle JRE (Hotspot VM) is the only tested and supported Java platform.
Supported platforms for Remedy SSO agents
Remedy SSO supports Remedy SSO agents running on the following operating systems versions or later versions.
- Windows Server 2008 R2
- Windows Server 2012
- Windows 2016
- Red Hat Enterprise Linux 6.x
- Red Hat Enterprise Linux 7.x
- CentOS 6.5
- Oracle Solaris 10
- AR authentication
- (Starting from version 9.1.01) Certificate-based authentication
- (Starting from version 9.1.01) Kerberos