Ticket validation error - COMMON CAUSES

The most common causes for Ticket Validation Error are:

1. The user has put the login screen page in their bookmarks and attempted to access the page again. This causes an expired request to be used again. Version 6.0 of Ubisecure SSO will redirect the user to a chosen service home screen in case of this event.
2. A user session has expired before the login has completed. Authentication request validity time can be made longer using the SAML SP for Java API

3. If the user tries to use the same login or logout links from one session in another session (e.g., with a different browser or on a different device)

4. If the browser does not support cookies or cookies are blocked from the site
5. If the user has tried to modify the sign-in URL by hand, e.g., by modifying the numbers shown in the URL.
6. If the user’s IP address is shown differently to the Ubisecure SSO as compared to the SP service. If this is unavoidable, this check can be be disabled by using the agent’s netmask setting.
7. If a TUPAS service sends an unsupported transaction type or code (for example some TUPAS 2.2 test services send non-compliant messages).

In these cases the text from the key TICKET_VALIDATION_ERROR in the file

custom/errors.properties is shown to the user. This text should be modified to suit the most common situation experienced by the users.