Configure a certificate mapping that lets SiteMinder determine how to compare user certificate information with the information stored in the user directory.
To configure a certificate mapping
The Create Certificate Mapping pane opens.
Note: Click Help for descriptions of settings and controls, including their respective requirements and limits.
When entering the DN, escape reserved special characters with a backslash (\). Special characters include:
More information about reserved special characters for DNs exists at http://www.faqs.org/rfcs/rfc2253.html.
Note: Issuer DNs cannot exceed 255 characters if a relational database is used as a policy store and cannot exceed 1000 characters if an LDAP directory is used as a policy store.
For LDAP directories only, you can configure the Policy Server to verify that the certificate the user presents matches the certificate stored in the user record in the user directory. The Certificate Required in Directory check box lets you require this verification.
Note: The certificate in the LDAP directory must be base64-encoded without embedded newlines.; Binary certificates, PEM certificates, and multiline base64-encoded certificates are not supported.
If you do not select CRLs, you can use OCSP.
The Create Certificate Mapping task is submitted for processing.
Testing a certificate mapping displays the search string the Policy Server is to use to map client certificates to user directory attributes.
To test a certificate mapping
The Certificate Map Test group box opens.
Note: The Directory list includes all of the existing directory connections of the type you selected when creating the certificate mapping.
The contents of the Directory Information group box change based on the type of user directory connection. For WinNT, ODBC and OCI user directory connections, the group box displays the Directory Type you are testing. For LDAP directory connections, the group box displays the Directory Type, as well as the Lookup Start and Lookup End values used to locate a user’s DN within the LDAP directory.
The Policy Server tests the certificate mapping and the Certificate Map Test group box provides the results.
Note: Click Help for descriptions of settings and controls, including their respective requirements and limits.
The Certificate Map Test group box closes.
You can use custom mapping expressions for complex multiple attribute mapping. This allows you to specify multiple user attributes that should be extracted from a user DN to establish a certificate mapping.
Note: Custom mapping expressions are also useful when simulating certificate-based authentications through the SiteMinder Test Tool.
The syntax for a custom mapping expression is a parsing specification designed to enable full mapping flexibility. It indicates which information to take from the certificate and where it should be applied to in the user directory. The basic syntax is as follows:
UserAttribute=%{CertificateAttribute},
UserAttribute2=%{CertificateAttribute}
When you create a custom certificate mapping for an LDAP user directory, the resulting search query string includes the LDAP User DN Lookup Start and End strings in addition to the Mapping Expression that you specify on the Create Certificate Mapping pane. The resulting query is invalid, as seen in the following example:
(samAccountName=
)
(mail=%{E})
(samAccountName=(mail=%{E}))
To omit the User DN Lookup Start and End strings from the search query, navigate to \Netegrity\SiteMinder\CurrentVersion\PolicyServer\ and set the EnableCustomExprOnly registry key to 1. The resulting search query string is valid, as seen in this example:
mail=%{E}
mail=%{E}
Note: If the EnableCustomExprOnly registry key is 0 (the default) or the key does not exist, the User DN Lookup Start and End strings are included in the resulting search query.
Using LDAP syntax to create search filters that contain logic operators requires you to enable the LegacyCertMapping registry key. Enabling the registry key allows legacy behavior in certificate mapping, which ensures that users are authenticated using the specified LDAP search criteria.
KeyType: DWORD
Values: 0 (disabled) and 1 (enabled)
Default: 0
To enable the registry key on Windows
Note: If a value other than 0x1 is set, or the registry value does not exist, the registry key is disabled.
LegacyCertMapping is enabled, and LDAP search filter syntax can be used with custom mapping.
To enable the registry key on UNIX
HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\ PolicyServer=XXXXX LegacyCertMapping=0X1 REG_DWORD
LegacyCertMapping is enabled, and LDAP search filter syntax can be used with custom mapping.
If a user’s certificate contains:
SubjectDN: CN=John Smith, UID=JSMITH, OU=development, O=CompanyA
You can specify the following custom mapping:
CN=%{UID}, OU=%{OU}, O=%{O}
The resulting UserDN is:
CN=JSMITH, OU=development, O=CompanyA
The custom mapping syntax also handles more complex mappings, as illustrated in the example:
If the user’s certificate contains:
Subject DN: CN=John Smith + UID=jsmith +EMAIL=jsmith@companyA.com, ou=development, o=companyA
You can specify the following custom mapping:
CN=%{CN.CN}+UID=%{CN.UID}, OU=%{O}
The resulting UserDN is:
CN=John Smith+UID=JSMITH, OU=companyA
In the above example, the CN contained multiple attributes. The syntax indicated which components of the CN to take and apply to the UserDN’s CN. This was done by specifying “CN.CN or CN.UID” This syntax indicates that the custom expression uses both the CN and UID parts of the CN.
Note: You cannot use the “+” operator to disambiguate multiple attributes in a user directory. The “+” operator is used like any other character in the user DN for a user that is present in the user directory.
Static text can be represented in a custom expression by leaving it outside of the bracket notation as shown below.
The user’s certificate contains:
Subject DN: CN=John Smith, UID=JSMITH, OU-development
You can specify the following mapping:
CN=%{UID}, OU=%{OU}, O=companyA
The resulting UserDN is:
CN=JSMITH, OU=development, O=CompanyA
For more information, see the next section.
The template string is composed of text and hash-bracketed expressions %{…}. All text outside the brackets is returned unchanged. The hash-bracketed expressions are evaluated based on the following rules:
Certificate Mapping supports mapping of the CertSerialNumber and IssuerDN attributes, which are not part of the subjectDN. These attribute(s) in the subjectDN of user certificates can be mapped to default or custom user-attribute(s), such as UID or CN in the user directory.
To map these attributes, add the following in the Mapping Expressions field in the Certificate Mapping pane:
Some certificates may have multiple attributes of the same type in their Subject DN. SiteMinder supports a simple method for using a custom certificate mapping to see attributes other than the first attribute of a particular type. The syntax is as follows:
%{attribute_name} for the first occurrence of attribute_name
%{attribute_nameN} for the Nth occurrence of attribute_name
If the Subject DN of the certificate contained CN=user,ou=dev,sn=1234,sn=2345,sn=3456,o=company,c=us, you could set up a custom certificate mapping to any of the sn attributes. For example, to map to the first sn, enter %{sn} as the custom mapping. To map to the second sn, you could enter %{sn2} as the custom mapping.
Sometimes certificates for individuals may be slightly different. For example, some users may have two account numbers, while others have a single number. In these cases, you may want to map to the second of the numbers when a second attribute exists. You can do so using the following notation:
%{attribute_name2/attribute_name}
Using the example from above, you could enter %{SN2/SN} as a custom mapping to indicate that the second number in the Subject DN should be used if it exists, otherwise, the first occurrence of the account number attribute should be used.
This notation can also be used to specify two different attributes that are acceptable for a certificate mapping. For example, to indicate that the SN should be used, but a CN may be used if the SN does not exist, you could enter %{SN/CN}.
|
Copyright © 2012 CA.
All rights reserved.
|
|