Because the AS Java always accepts its own tickets, you should use two separate servers to test the use of logon tickets. Configure one as the issuing server and a different one to accept the logon tickets from the first server.
If the AS Java is the ticket-issuing server, then you can use one of the example programs provided with the server, such as Hello. The application is deployed on the ticket-issuing AS Java and its login module stack is configured to authenticate the user and then create a logon ticket.
If you do not set your Web browser to prompt for cookies, then alternatively you can verify the use of logon tickets in the security log using the Log Viewer. The corresponding log is security.log under Cluster → Server → .\log → system.
Testing the Creation of Logon Tickets
You receive several cookies.
The logon ticket is a cookie with the name MYSAPSSO2.
The message New SAP Logon Ticket for user <user_ID> has been created. in the security log indicates that the logon ticket has been created successfully for the user.
Testing the Use of Logon Tickets for Successive Access
Using the same Web browser as you used for the first test, access the test application for using logon tickets.
You should receive access to the application without having to authenticate yourself. If you are not allowed access, then Single Sign-On using logon tickets is not set up correctly.
The message Ticket verify of user <user_ID> successful. in the security log indicates that the logon ticket was used for authentication on the server.
Possible Reasons for Unsuccessful Single Sign-On