Administrator Guide

Administrator Guide

RTAM Authentication

RTAM Authentication

When users log in to RTAM, the user’s credential is authenticated using the authentication provider (whether local or external) and mechanism configured for this implementation. Every user authenticated is granted full access to the application.
By default, RTAM authenticates users using the RulePoint database as the provider and Form authentication as the mechanism. In addition, you can configure RTAM to authenticate using the RulePoint database as the provider with Basic authentication as the mechanism, or using an external authentication server as the provider and Basic, Form, or PKI for Public Key Infrastructure (X.509 client certificates) authentication as the mechanism.
RTAM supports only standard LDAP constructs.
Options
The following table provides you with an overview of the possible choices for configuring authentication in RTAM:
Authentication options
Mechanism
Provider
Basic
Form
RTAM database
X
X1
Lightweight Directory Access Protocol (LDAP) Server
X
X
Microsoft Active Directory (AD) via LDAP
X
X
X.509
n/a
n/a
RTAM does not support changing authentication providers after you have configured and begun using RTAM. To change authentication providers, you must drop the RTAM database and re-configure the external authentication server. Not all authentication mechanisms can be applied to all authentication provider directories, and supported options might also differ by container. For more information, see your authentication provider documentation.
Choose a Default Authentication Provider
RTAM supports three other authentication providers other than the default RTAM RulePoint database authentication and Form authentication as the mechanism. To change the default authentication, you can select one of three options
  • If you are configuring RTAM to use LDAP, you must edit the contextConfigLocation property in the web.xml file located in the [RTAMHome]\WEB-INF\folder to read as follows:
    <context-param> <param-name>contextConfigLocation</param-name> <param-value> /WEB-INF/classes/spring-context.xml /WEB-INF/classes/
    security-ldap.xml
    </param-value> </context-param>
  • If you are configuring RTAM to use OpenLDAP, you must edit the contextConfigLocation property in the web.xml file that is located in the [RTAMHome]\WEB-INF\ folder to read as follows:
    <context-param> <param-name>contextConfigLocation</param-name> <param-value> /WEB-INF/classes/spring-context.xml /WEB-INF/classes/
    security-openldap.xml
    </param-value> </context-param>
  • If you are configuring RTAM to use X509, you must edit the contextConfigLocation property in the web.xml file that is located in the [RTAMHome]\WEB-INF\ folder to read as follows:
    <context-param> <param-name>contextConfigLocation</param-name> <param-value> /WEB-INF/classes/spring-context.xml /WEB-INF/classes/
    security-X509.xml
    </param-value> </context-param>

0 COMMENTS

We’d like to hear from you!