Parameters for LDAP configuration
SSX provides a common interface for other IBM® webMethods products to use LDAP v3 (RFC 4510) compliant directory services for authentication purposes. If issues arise while using SSX as a client for an LDAP service, IBM will analyze and provide support for problems that can be reproduced with an OpenLDAP 2.4 server running on a supported UNIX system, a Red Hat Directory Server running on a supported Red Hat Enterprise Linux system, or a Microsoft Active Directory server running on a supported Windows Server platform.
The following configuration parameters are used for authentication against an LDAP server.
| Parameter | Description |
|---|---|
| authType | The user database type. The required value is No default value. |
| serverHost | The URL, name or IP address of the server. It may optionally be followed by a colon (:) and
the port number. In the latter case, the serverPort parameter is ignored. A
valid value is any valid No default value. |
| serverPort | Optional. The port of the server. A valid value is any valid port number. The default value is:
|
| homeDir | Optional. An absolute path to an existing directory. It may either be the directory
containing the SSX installation (as in The ssxconfig file, which may contain the TLS configuration and the common LDAP server configuration, is looked for at the given directory. See TLS/SSL configuration and common defaults for multiple LDAP servers. No default value. |
| serverType | Optional. The name of the common LDAP server configuration as set up in the ssxconfig file. A valid value is any name as specified as the second part in the default LDAP configuration, for
example, Suggested values:
No default value. |
| personBindDn | The Distinguished Name where the authentication information is stored. This value will be
prefixed with the value of the userIdField parameter when issuing the
authentication call. Valid values (example):
No default value. |
| groupBindDn | The Group Root Distinguished Name (DN) for LDAP where the search for group names starts.
This value will be prefixed with the value of the groupIdField parameter when
issuing the authentication call. Valid values (example):
No default value. |
| personObjClass | Optional. The object classes of the user entries. Valid values:
Overrides the common configuration parameter in |
| groupObjClass | Optional. The object classes of the group entries. Valid values:
Overrides the common configuration parameter in |
| personGrpAttr | Optional. The property name of a user entry that points to the group in which the user is a member. Valid values:
Overrides the common configuration parameter in |
| groupPrsAttr | Optional. The property name of a user entry that points from the group to the respective users. Valid values:
Overrides the common configuration parameter in |
| userIdField | Optional. The property name that denotes the user ID. Valid values:
Overrides the common configuration parameter in |
| groupIdField | Optional. The property name that denotes the group ID. Valid values:
Overrides the common configuration parameter in |
| passwdField | Optional. The property name that denotes the password field of a user entry. Valid values:
Overrides the common configuration parameter in |
| addPersonAttr | Optional. May contain additional fields and values that are used when a new user is
added. The string Valid values:
Overrides the common configuration parameter in |
| addGroupAttr | Optional. May contain additional fields and values that are used when a new group is
added. The string Valid values:
Overrides the common configuration parameter in |
| allowDomainAsBaseBindDn | Optional. Boolean. If the domain name is not specified explicitly and the
defaultDomain parameter is set, this value is interpreted as
Valid values:
|
| personPropAttr | Optional. The user's properties of interest. A valid value is a comma-separated list that contains the property names:
The property names are amended by an indicator signifying whether the property is read-only
( The list with property names for a user entry is empty in the following cases:
Overrides the common configuration parameter in |
| groupPropAttr | Optional. The group's properties of interest. A valid value is a comma-separated list that contains the property names:
The property names are amended by an indicator signifying whether the property is read-only
( The list with property names for a group entry is empty in the following cases:
Overrides the common configuration parameter in |
| ldapStartTls | Optional. Boolean. If true, try to set up an encrypted communication over the plain LDAP port if the LDAP server supports it. Ensure to properly set up the ssxconfig file. See TLS/SSL configuration and common defaults for multiple LDAP servers for instructions. Ignored if a TLS/SSL-secured communication to the LDAP server is configured, for example, through
the ldapSSLConnection parameter or by specifying an Valid values:
|
| resolveGroups | Optional. The method for finding the groups of a user using the LDAP authentication type. Valid values:
|
| computedGroupProp | Optional. The name of an LDAP property. It is activated if
resolveGroups is set to Valid values:
No default value. |
| ldapSSLConnection | Optional. Boolean. If true, a TLS/SSL secured communication to the LDAP server is enforced. Ensure to properly set up the ssxconfig file. See TLS/SSL configuration and common defaults for multiple LDAP servers for instructions. Valid values:
|
| followReferrals | Optional. Boolean. If true, try to follow LDAP server referrals. Valid values:
|
| refServerBindingType | Optional. The kind of binding during Valid values:
|
| referralHopsCnt | Optional. The count of the referral hops. If this parameter is not specified, the count is unlimited. A valid value is any positive integer. The default value is unlimited. |
| useLdapTechUser | Optional. Boolean. Enables the usage of a technical user. Valid values:
|
| techLdapUserCredFile | Mandatory only if you enable the usage of a technical user. The path of the technical user credentials file. A valid value is any valid directory and file name on the file system. No default value. For more information, see Creating technical user credential files. |
| techLdapUserKeyFile | Mandatory if a key file was used to create the technical user credentials file. The path of the key file. A valid value is any valid directory and file name on the file system. No default value. For more information, see Additional information about key files. |
| ldapTimeout | Optional. The number of seconds after which a long running LDAP operation is canceled. Overrides the common configuration parameter in |
| ldapSaslBind | Optional. Boolean. Whether or not an SASL authentication is to be used on this LDAP connection. Note:
The SASL mechanism Valid values:
|