This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Logon Ticket Cache" – news · newspapers · books · scholar · JSTOR (January 2014) (Learn how and when to remove this message) The topic of this article may not meet Wikipedia's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources: "Logon Ticket Cache" – news · newspapers · books · scholar · JSTOR (January 2014) (Learn how and when to remove this message) (Learn how and when to remove this message)

Logon ticket cache is related to SAP Logon Tickets. The logon ticket cache is intended to make the SAP logon procedure. Logon tickets are stored in cache memory (shared memory). The SAP Web Application Server will search for the logon ticket through its system cache memory. If the system finds the user's logon information, the system does not carry out a signature check. The logon ticket cache will remain in SAP Web Application Server until the expiration of the logon ticket. There is a hash procedure for securing cache entries.

On a given SAP Web Application Server you can:

• Create logon tickets with certificates
• Create logon tickets without certificates
• Configure the web AS to accept logon tickets

• SAP GUI
• Secure Network Communications

• Logon Ticket Cache