Login Headers

The login headers are used for single sign-on login modules such as LDAP, SiteMinder, TAM and also for CustomLoginModule if it is configured and the overridden method isHeaderRequired returns true. 
For more information on the CustomLoginModule, refer to the sectionSetting Up a Custom Authentication Handler.

For login headers, UserName and Enterprise are mandatory parameters. The user is expected to provide the HTTP or Soap headers based on the login module configured in Configurator. For example, LDAP or 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}. For information on the LDAP header properties and their values, refer to Default/LDAP Properties.
  • HTTP/Soap headers for SiteMinder: For example, SM_FIRSTNAME. In this case, if you have specified John as first name, the header populates {SM_FIRSTNAME,JOHN}. For information on the SiteMinder header properties and their values, refer to 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. The login module authenticates the login information. If the required information is not provided in the respective header, then the login module displays an error.

    The identity section of web services include:

    • UserName
    • Enterprise
    • Password

      If identity is specified, no other headers are required. However, if headers are specified, headers takes 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 on the default header handling for UI and web services, refer to Default Implementation for UI and Web Services.