Chained functions combine authentication subsystems. The chain is controlled by the authentication.chain global property. When a user logs in, Alfresco tries the user's credentials against each of the subsystems in the order specified in the chain, until the credentials are accepted (the login is successful) or until each subsystem has been tried (and the login fails).
Some functions cannot be chained (passthru function), for example, CIFS authentication, and NTLM / SPEGNO based Single Sign-On (SSO). These functions are handled by the first subsystem in the chain that supports that function and has it enabled. This means that only a subset of your users might be able to use SSO and CIFS.
If Kerberos is configured along with basic authentication in a chain, all the calls to the repository will only support Kerberos. The response from the server only contains the WWW-Authenticate: Negotiate header.
- Set the following property (true, by default):
- Send a basic authentication header in all the requests.
Authorization: Basic <encoded_string>where <encoded_string> is a base64 encoded username and password separated by a single colon (:). For more information, see Basic Authentication Scheme.
To configure the authentication chain, follow the steps below:
- Open the alfresco-global.properties file.
Locate, or if it does not already exist, create the
authentication.chain global property.
This is a comma separated list of the form:
Set the property to the required values.
The default authentication chain specifies one instance of the alfrescoNtlm subsystem type with ID alfrescoNtlm1.
For example, set the property to the following value:
When you navigate to the Alfresco:Type=Configuration,Category=Authentication,id1=manager MBean in global property overrides, a new authentication subsystem instance called ldap1 is created and added to the end of the authentication chain.
- Save the file.
- Built-in Alfresco users and Windows users can log in, with Alfresco taking precedence
- The Windows domain server handles CIFS authentication directly
- LDAP synchronizes user and group details
- Configure the following authentication
- Deactivate SSO in order to activate chained password-based log in, target CIFS at
passthru1 and target synchronization (but not authentication) at
ldap1 by setting the following properties:
- User passwords are validated directly against the LDAP servers for web, SharePoint and FTP login
- The CIFS server is deactivated because neither server can handle CIFS-style authentication
- LDAP is used to synchronize user and group details from both directories
- Users in the first directory, ldap1, take precedence over those in the second directory, ldap2
- In the alfresco-global.properties, specify this
- Copy ldap-authentication.properties to both the <classpathRoot>/alfresco/extension/subsystems/Authentication/ldap/ldap1/ldap-authentication.properties and <classpathRoot>/alfresco/extension/subsystems/Authentication/ldap/ldap2/ldap-authentication.properties files.
- Edit the properties for ldap1 and ldap2 with appropriate settings to complete the configuration. See LDAP configuration properties for information on each of the properties.