Policy Server Guides › Policy Server Configuration Guide › Authentication Schemes › SecurID Authentication Schemes › Configure a SecurID Authentication Scheme

Configure a SecurID Authentication Scheme

You use a SecurID authentication scheme to authenticate users logging in with ACE credentials.

Note: The following procedure assumes that you are creating an object. You can also copy the properties of an existing object to create an object. For more information, see Duplicate Policy Server Objects.

To configure the authentication scheme

1. Click Infrastructure, Authentication.
2. Click Authentication Scheme, Create Authentication Scheme.

   The Create Authentication Scheme pane opens.

3. Click OK.

   Authentication scheme settings open.

   Note: Click Help for descriptions of settings and controls, including their respective requirements and limits.

4. Select SecurID Template from the Authentication Type Style list.

   Scheme-specific fields and controls open.

5. Enter a name and a protection level in the General group box.
6. Enter the ACE User ID attribute in the Scheme Setup group box.
7. Click Submit.

   The authentication scheme is saved and may be assigned to a realm.

SecurID with HTML Forms Support Scheme Prerequisites

Ensure the following prerequisites are met before configuring a SecureID with HTML authentication scheme:

• The RSA ACE/Client software is installed on the same machine as the Policy Server.
• For Policy Servers on Windows, the ACE configuration information file (sdconf.rec) resides in the winnt\system32 directory. The VAR_ACE and USR_ACE variables are pointing to the appropriate ACE agent data and prog directories respectively.
• For Policy Servers on UNIX, the sdconf.rec file resides in the <policy server installation dir>/lib directory. In addition, the VAR_ACE and USR_ACE variables are pointing to the <policy server installation dir>/lib, allowing the Policy Server to use SiteMinder API libraries and not the ACE agent.
• A customized .fcc file resides on a Web Agent server in the cookie domain in which you want to implement HTML Forms authentication. CA provides sample .fcc files under the Samples/Forms subdirectory, where you installed your Web Agent.
• A customized .unauth file resides on the Web Agent server.

  Note: The .unauth file is not required if the .fcc file uses the smerrorpage directive.

• A directory connection exists between the Policy Server and the user directory.
• The default HTML forms library is installed. This library handles HTML Forms authentication processing:
  • SmAuthHTML.dll on Windows
  • smauthhtml.so on Solaris

  These files are installed automatically when you configure a Web Agent.

More information:

SiteMinder FCC Files

User Directories