Login Headers

The login headers are used for single sign-on authentication such as SiteMinder.

For login headers, Username and Enterprise are mandatory parameters. The user is expected to provide the HTTP or Soap headers based on the authentication type. For example, SiteMinder.

• HTTP/Soap headers for LDAP: For example, FIRSTNAME. In this case, if you have specified John as first name, the header populates {FIRSTNAME,JOHN}.
• HTTP/Soap headers for SiteMinder and OIDC: For example, SM_FIRSTNAME. In this case, if you have specified John as first name, the header populates {SM_FIRSTNAME,JOHN}. For information about the SiteMinder header properties and their values, see Single Sign-On Properties.

The login headers apply to UI and web services.

• For UI: Login accepts HTTP headers. When TIBCO MDM UI is used to login, the user identification is captured in the UI and no other information is needed. However, when TIBCO MDM UI is invoked through redirection, the login information must be specified in the HTTP headers.
• For web services: Login accepts Soap headers. When a web service is executed, login information must be included in the soap header element of a web service. If the required information is not provided in the respective header, then the login module displays an error.

  The identity section of web services includes:

  • UserName
  • Enterprise
  • Password

    If identity is specified, no other headers are required. However, if headers are specified, headers take precedence over the identity information. Note that if auto user creation or modification is set, additional headers are usually provided. The custom headers can replace the identity section in web services.

    Example of default login headers in web services:

    <soapenv:Header><enterprise>a</enterprise><user>a</user></soapenv:Header>

    For more information about the default header handling for UI and web services, see Default Implementation for UI and Web Services.