Start of Content Area

Background documentation SAP Logon Ticket  Locate the document in its SAP Library structure

Note

For these properties to apply, the login modules that apply to tickets (CreateTicketLoginModule and EvaluateTicketLoginModule) must have the following option set:

ume.configuration.active = true

Property

Value

Description

login.ticket_client

A three-character numeric string.

Default value is 000.

The client that is written into the SAP logon ticket. This value is used to differentiate the AS for Java from the AS for ABAP. Systems are identified by the client and system ID (SID). In a combined installation the AS for Java and AS for ABAP have the same SID, so you must identify the AS for Java with a client number that is not in use by the AS for ABAP.

Set or change this value in an Add-In installation.

login.ticket_lifetime

Default value is 8.

Number of hours that the logon ticket is valid.

You can also have values of the form hh:mm.

login.ticket_portalid

Default value is AUTO.

YES = The portal ID is always written into the logon ticket.

NO = The portal ID is never written into the logon ticket.

AUTO = If a portal installation is detected, the portal ID is written into the logon ticket.

The system always writes the ABAP user ID into the log on ticket. You can configure the system to write in the portal user ID only when it is necessary, or you can force the system to always include the portal ID. This enables you to support passwords longer than 8 characters.

ume.login.mdc.hosts

Enter a comma separated list of servers:

Syntax

<protocol>://<host>:<port>/<path>

For example:

http://server.example.com

Only the host value is mandatory in all cases. For more information about the syntax, see   Configuring SAP Logon Tickets for Multiple Domains

This property enables the portal to solicit logon tickets from servers outside the portal domain. For more information, see SAP Logon Tickets for Multiple Domains.

ume.logon.
httponlycookie

true or false

Default value is true.

If true, the SAP logon ticket is set to HttpOnly. This prevents it from being read by malicious client-side script code such as JavaScript.

The setting is only effective for clients that use Microsoft Internet Explorer 6.0 SP1 or higher.

ume.logon.security.
enforce_secure_cookie

true or false

Default value is false

Marks the SAP logon ticket as a secure cookie, to enforce that the client browser sends the cookie only when an SSL connection to the J2EE Engine or the reverse proxy is established.

ume.logon.security.
relax_domain.level

Default value is 1.

Specifies the amount of sub domains to remove from the server name to obtain the domain for which the SAP logon ticket is valid.

For example, if the value is 1 and the logon ticket is issued by the server server.mycompany.com, the logon ticket is valid for all servers in the domain mycompany.com.

 

End of Content Area