One of our users is suddenly unable to log on Tessitura and when they try get the error message "The provided resource security token has expired".
The problem appears to be workstation specific, as the user is able to log in to Tess on another computer and when other users log in to her workstation they get the same error message.
Has anyone else encountered this error before?
Sarah
This error is usually due to the workstation date/time not matching that of the server. (This is important for certain types of authentication.)
Double-check the system time -- if possible, sync with a network time server. Make sure also that you are in the correct time zone and date, since I believe it's something like UTC (a global absolute time) that is being checked.
Thanks Nick & Sandra. That was my first thought too but we checked and the workstation time appears to be in synch with the server.
Hi Sarah
The "provided resource security token has expired" error usually points to a date/time issue between the REST Services server
and the workstation. If the date/times are not in sync then this error can occur. It usually needs to be within 5 minutes of each
other, otherwise you'll see this error.
Cheers
Sandra
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Sarah Coffey Sent: Tuesday, October 6, 2015 1:07 PM To: Sandra Ashby <sashby@tessituranetwork.com> Subject: [Tessitura Technical Forum] The provided resource security token has expired
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
We went back and double checked, and it turned out that the user failed to let us know that they had manually adjusted the time, so although the time looked like it was matched the time zone settings hadn't been updated correctly.
And this thread just saved our life here at the Sydney Symphony this morning. Thank you!