Documentation Center

Identities

An identity allows you to capture Web pages that have been personalized.

Personalization can be based on:

  • the profile of a visitor as defined in a Target Group and set using a Profiling and Personalization Cookie
  • the authentication credentials required for a user (a username and password, and optionally a requesting host and authentication realm)
  • HTTP request header information for differentiating responses

The following code is an example of an <Identity>:

<Identity Name="profile-2" Username="user" Password="password" Domain="domain.com">
  <HttpHeader Name="headername" Value="headervalue"/>
  <Cookie Name="cookiename" Value="cookievalue"/>
</Identity>

An <Identity> can consist of the following sections:

Identity
In the Identity element, specify a logical name and optionally credentials and one or more Httpheaders and Cookies elements:
  • Name — a logical name for the user profile
  • Username — a user logon name
  • Password — a user logon password
  • Domain — (optional) specify a realm and host
  • AltRedirect — (optional) set to true if your Web site uses redirect functionality, otherwise false
HttpHeaders
In the HttpHeaders element, define a name/value pair containing (a String value). You can use the HTTP Header element to define (custom) situations where the server response varies depending on the information sent by the browser in the request header:
  • Name — set the HTTP header name
  • Value — set the HTTP header value
Cookie
In the Cookie element, you need to relate the identity to a user profile by specifying:
  • Name — set the cookie Name to correspond with the Name of the cookie that sets user profile information in the cd_wai_conf.xml file
  • Value — set the cookie Value to an ID of a profiled user (the IDs are stored in the Content Data Store database)