Hannon Hill Corporation

Set LDAP Imported Users as Using Custom Authentication

Beginning with Cascade Server 4.2, Administrators may specify within a new <authentication-mode> element whether to use "normal", "custom", or "ldap" authentication:

This element overrides the <authenticate-against-ldap-server> policy level configuration element, which allowed only "yes", "no", without allowing for custom authentication modes.

Inside the user policy, the element will look like this:

<user-policy summary="Main Employees"> <container-identifier>OU=Employees,DC=hannonhill,DC=com</container-identifier> <object-attribute-filter> <name>objectCategory</name> <value>CN=Person,CN=Schema,CN=Configuration,DC=hannonhill,DC=com</value> </object-attribute-filter> <username-attribute>sAMAccountName</username-attribute> <email-attribute>userPrincipalName</email-attribute> <full-name-attribute>displayName</full-name-attribute> <enable-new-users>yes</enable-new-users> <convert-usernames-to-lowercase>yes</convert-usernames-to-lowercase> <authentication-mode>custom</authentication-mode> <system-groups remove-from-other-groups="yes"> <group> <name>development</name> </group> </system-groups> <system-roles remove-from-other-roles="yes"> <role>Administrator</role> <role>Publisher</role> </system-roles> </user-policy>