Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Single Sign-on in a Multi-directory World: "Never say login again" Part 2

Sing sign-on scenarios

Return to article

For Your Eyes Only if you are a Quickplace administrator

Here is the information you need to configure Quickplace, if using the LDAP protocol to look up users and perform name mapping.

Configure special search prefix filters

The search filter begins with the string prefix defined by the QuickPlaceRemapDN variable in the Domino server's Notes.ini file, and ends at the next separator. Quickplace uses the value of QuickplaceRemapDN to key on the characters that precede the user name text string to be compared. So for example:

  • If the LTPA cookie contains a DN such as: uid=jb013, ou=secret, dc=spies, dc=com
  • and the Quickplace server should search on uid=jb013

then the prefix is uid=. This means the Notes.ini setting would be:

QuickplaceRemapDN=uid=

This can be a multi-valued, semi-colon separated prefix list, for example:

QuickplaceRemapDN=uid=;cn=

Note that Quickplace cannot handle asterisks in these Notes.ini variables.

Special considerations for Domino person documents

The Domino person document must be modified to contain the contents of the LDAP attribute specified in QuickPlaceRemapDN. The value of the attribute type configured in QuickPlaceRemapDN must be added as a secondary value in the FullName field of a Domino person document. This is because the LDAP filter searched will contain this value (for example, jb013).

So for Jim Bland, his person document must contain both uid=jb013,ou=secret,dc=spies,dc=com AND jb013 (see figure 1):


Figure 1. LDAP attribute
LDAP attribute

Return to article