AEM forms provides two ways to enable single sign-on (SSO) - HTTP headers and SPNEGO.
When SSO is implemented, the AEM forms user login pages are not required and do not appear if the user is already authenticated through their company portal.
If AEM forms cannot authenticate a user by using either of these methods, the user is redirected to a login page.
You can use the Portal Configuration page to enable single sign-on (SSO) between applications and any application that supports conveying the identity over HTTP header. When SSO is implemented, the AEM forms user login pages are not required and do not appear if the user is already authenticated through their company portal.
You can also enable SSO by using SPNEGO. (See Enable SSO using SPNEGO.)
In administration console, click Settings > User Management > Configuration > Configure Portal Attributes.
Select Yes to enable SSO. If you select No, the remaining settings on the page are unavailable.
Set the remaining options on the page as required and click OK:
SSO type: (Mandatory) Select HTTP Header to enable SSO using HTTP headers.
HTTP header for user’s identifier: (Mandatory) Name of the header whose value contains the logged-in user’s unique identifier. User Management uses this value to find the user in the User Management database. The value obtained from this header should match the unique identifier of the user who is synchronized from the LDAP directory. (See User settings.)
Identifier value maps to user’s User ID instead of user’s unique identifier: Maps the user’s unique identifier value to the User ID. Select this option if the user’s unique identifier is a binary value that cannot be easily propagated through HTTP headers (for example, objectGUID if you are synchronizing users from Active Directory).
HTTP header for domain: (Not mandatory) Name of the header whose value contains the domain name. Use this setting only if no single HTTP header uniquely identifies the user. Use this setting for cases where multiple domains exist and the unique identifier is unique only within a domain. In this case, specify the header name in this text box and specify domain mapping for the multiple domains in the Domain mapping box. (See Editing and converting existing domains.)
Domain mapping: (Mandatory) Specifies mapping for multiple domains in the format header value=domain name.
For example, consider a situation where the HTTP header for a domain is domainName, and it can have values of domain1, domain2, or domain3. In this case, use domain mapping to map the domainName values to User Management domain names. Each mapping must be on a different line:
For the steps to configure allowed referers, see Configure allowed referers.
You can use Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) to enable single sign-on (SSO) when using Active Directory as your LDAP server in a Windows environment. When SSO is enabled, the AEM forms user login pages are not required and do not appear.
You can also enable SSO by using HTTP headers. (See Enable SSO using HTTP headers.)
AEM Forms on JEE does not support configuring SSO using Kerberos/SPNEGO in a multiple child domain environments .
Decide which domain to use to enable SSO. The AEM forms server and the users must be part of the same Windows domain or trusted domain.
In Active Directory, create a user who represents the AEM forms server. (See Create a user account.) If you are configuring more than one domain to use SPNEGO, ensure that the passwords for each of these users is different. If the passwords are not different, SPNEGO SSO does not work.
Map the service principal name. (See Map a Service Principal Name (SPN).)
Configure the domain controller. (See Prevent Kerberos integrity-check failures.)
Add or edit a directory that contains your Active Directory information.
Add LDAP as an authentication provider.
Add Kerberos as an authentication provider. Provide the following information on the New or Edit Authentication page for Kerberos:
ipconfig/allon the command line.
Configure SPNEGO client browser settings. (See Configuring SPNEGO client browser settings.)
In SPNEGO, register a service as a user in Active Directory on the domain controller to represent AEM forms. On the domain controller, go to Start Menu > Administrative Tools > Active Directory Users And Computers. If Administrative Tools is not in the Start menu, use the Control Panel.
Click the Users folder to display a list of users.
Right-click the user folder and select New > User.
Type the First Name/Last Name and User Logon Name and then click Next. For example, set the following values:
Type a password. For example, set it to password. Ensure that Password Never Expires is selected and no other options are selected.
Click Next and then click Finish.
Obtain the KtPass utility. This utility is used to map an SPN to a REALM. You can obtain the KtPass utility as part of Windows Server Tool pack or Resource Kit. (See Windows Server 2003 Service Pack 1 Support Tools.)
In a command prompt, run
ktpass using the following arguments:
ktpass -princ HTTP/host
For example, type the following text:
ktpass -princ HTTP/lcserver.um.lc.com@UM.LC.COM -mapuser spnegodemo
The values that you must provide are described as follows:
host: Fully qualified name of the forms server or any unique URL. In this example, it is set to lcserver.um.lc.com.
REALM: The Active Directory realm for the domain controller. In this example, it is set to UM.LC.COM. Ensure that you enter the realm in uppercase characters. To determine the realm for Windows 2003, complete the following steps:
user: The login name of the user account you created in the previous task. In this example, it is set to spnegodemo.
If you encounter this error:
DsCrackNames returned 0x2 in the name entry for spnegodemo. ktpass:failed getting target domain for specified user.
try specifying the user as firstname.lastname@example.org:
ktpass -princ HTTP/lcserver.um.lc.com@UM.LC.COM -mapuser spnegodemo
For SPNEGO-based authentication to work, the client computer must be part of the domain the user account is created in. You must also configure the client browser to allow SPNEGO-based authentication. As well, the site that requires SPNEGO- based authentication must be a trusted site.
If the server is accessed by using the computer name, such as https://lcserver:8080*,* no settings are required for Internet Explorer. If you enter a URL that does not contain any dots (“.”), Internet Explorer treats the site as a local intranet site. If you are using a fully qualified name for the site, the site must be added as a trusted site.
Configure Internet Explorer 6.x
Configure Mozilla Firefox
In the browser URL box, type
The about:config - Mozilla Firefox dialog box appears.
In the Filter box, type
In the list shown, click network.negotiate-auth.trusted-uri and type one of the following commands as appropriate for your environment:
.um.lc.com- Configures Firefox to allow SPNEGO for any URL that ends with um.lc.com. Ensure that you include the dot (“.”) at the beginning.
lcserver.um.lc.com - Configures Firefox to allow SPNEGO for your specific server only. Do not start this value with a dot (“.”).
Test the configuration by accessing the application. The welcome page for the target application should appear.