Policy Server Guides › Policy Design Guide › Authentication Scheme and Related Dialogs Reference › Authentication Scheme Dialog › Authentication Scheme Dialog—SecurID HTML Form Template › Authentication Scheme Dialog—SecurID HTML Form Template—Scheme Setup Tab

Authentication Scheme Dialog—SecurID HTML Form Template—Scheme Setup Tab

The Scheme Setup tab for SecurID HTML Form authentication is where you enter the server, target, and ACE attribute for SecurID authentication with HTML forms support.

Web Server Name

Specifies the fully qualified domain name of the web server on which the FCC was installed.

Note: IP addresses are not supported.

The server does not have to be the same server on which the Agent is installed. Domain names must contain at least 2 periods and be specified using the following format:

servername.host.com:[port]

Example: server1.security.com. The port is only required for communication over a non–default port.

Note: If your network includes multiple cookie domains, configure a separate HTML Forms authentication scheme in each cookie domain in which you want to implement HTML Forms authentication.

Use SSL Connection

Select this check box if you want SiteMinder to use an SSL connection to process HTML Forms authentication.

Target

Specifies the path SiteMinder uses to process SecurID authentication with HTML forms support. This Target value assumes that the Web Agent receiving the request processes the password services. If password services templates reside on another Web Agent, the full path to that target URL is required.

Default: /siteminderagent/forms/smpwservices.fcc

ACE User ID Attribute Name in Directory

Specifies the attribute that contains ACE IDs.

If user distinguished names (DNs) are different from the ACE server’s user IDs, enter the name of the attribute in the user directory that contains the user ID in the ACE server. For example, if the ACE user ID is jsmith and the DN in an LDAP directory is cn=Jane Smith, ou=sales, o=security.com, you can map the user profile attributes back to the ACE user ID. In this example, you can create an attribute named aceid or use an existing unused attribute. The Policy Server retrieves the value of this attribute and uses it as the ACE user ID