What it means
The web server rejected the user's SSO token because its time stamps did not make sense against the server's own clock, so the user has to sign in again.
Common causes
- The clocks on servers sharing the Web SSO Configuration are out of step
- Wrong time zone or daylight saving settings on one server
- The token was issued by another server (such as a Sametime or WebSphere server) with a different clock
Quick fixes
- Synchronise all servers in the SSO domain to the same NTP time source
- Check the time zone and daylight saving settings on each server's operating system
- Clear the browser cookies, then sign in again to get a fresh token
- Check the Web SSO Configuration document is the same on all participating servers
Disclaimer
The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.
This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.