Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 > Administering > Managing the application server > Configuring authentication

Configuring authentication

By default, Cloud Cruiser authenticates users using its internal database to manage credentials. You can configure Cloud Cruiser to integrate with an external authentication system, such as an LDAP server or an SSO (Single Sign-On) system. To configure authentication, you must create a text file named <install_dir>/apache-tomcat-7.0.54/webapps/ROOT/WEB-INF/classes/ The contents of the file depend on the specific authentication system used and are detailed below in the appropriate section.

Internal authentication

Internal is the default configuration. It will be used if there is no file present. Alternately, you can explicitly configure internal authentication. The syntax of the file for URL is:


LDAP authentication

The syntax of the file for LDAP is:


The properties referenced by this syntax are:

<server_name> Host name or IP address of the LDAP server.

Port on which the LDAP server is listening (typically 389).


The Distinguished Name (principal) to use for obtaining authenticated LDAP contexts (administrator or manager access). For example, cn=Manager,dc=mycompany,dc=com.

Ensure that your Active Directory user is enabled. For example, Microsoft AD LDS users are disabled by default.


The password corresponding to the ldap.adminDN value.

<baseDN> An optional DN that will be combined with the ldap.userDNPattern or ldap.userSearchPattern value when matching users. For example, ou=My Organization,dc=mycompany,dc=com.

Pattern used to match users in the LDAP directory. The special token {0} will be replaced with the username being authenticated. For example,


User search pattern typically used in Active Directory configurations as an alternate to ldap.userDNPattern. The special token {0} will be replaced with the username being authenticated. For example, (&(&(objecClass=user)(objectCategory=person))(userPrincipalName={0})).


The attribute of the user object (objectClass) that contains the password to be verified against. For example, userPassword.

For example:


You must specify at least one of ldap.userDNPattern or ldap.userSearchPattern. If you specify both, Cloud Cruiser will first attempt to match against ldap.userDNPattern. If no match is found, Cloud Cruiser will then try to match against ldap.userSearchPattern.

ldap.baseDN is optional. If present, it will be combined with ldap.userDNPattern and ldap.userSearchPattern when matching users.

SSO authentication

Cloud Cruiser SSO configurations utilize http headers. The syntax of the file for SSO is:


The properties referenced by this syntax are:


Name of the HTTP header that will contain the username. This property is required.


Name of the HTTP header that specifies whether the user is enabled. This property is optional. If not defined, the user is always considered enabled.


The value of the sso.enablementHeaderName that indicates a user is enabled. This property is optional.

If specified, the user will be considered enabled only if the value specified matches the value of sso.enablementHeaderName. If this property is not specified, the user is considered enabled based on the presence of sso.enablementHeaderName (with any or no value).

<logoutURL> If specified, the application will redirect to this URL when the user logs out. This property is optional.


If this value is "true," unrecognized users (users who have not logged into Cloud Cruiser) will be created with default values. If the value is "false," unrecognized users will not be permitted to login. The default value is "false." This property is optional.

The following video shows how to configure Cloud Cruiser for SSO authentication:


Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP