tag:blogger.com,1999:blog-4463898250776378608.post3837925378423461612..comments2023-04-16T10:50:52.786+02:00Comments on Koen van der Linden's SharePoint Blog: SharePoint issue “The context has expired and can no longer be used. Exception from HRESULT 0x80090317”Koen van der Lindenhttp://www.blogger.com/profile/09745561653129473651noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4463898250776378608.post-26757104628447454732014-02-22T15:15:29.605+01:002014-02-22T15:15:29.605+01:00TokenTimeout is per WebApplication, so you cannot ...TokenTimeout is per WebApplication, so you cannot set this for a specific user.<br />A solution might be that the workflow impersonates a specific 'read-only' SPUser that does exists (that you created by deployment) and let the workflow do the necessary actions.Koen van der Lindenhttps://www.blogger.com/profile/09745561653129473651noreply@blogger.comtag:blogger.com,1999:blog-4463898250776378608.post-51669088440129616902014-02-21T22:38:58.542+01:002014-02-21T22:38:58.542+01:00We have exact same issue where we need to kickoff ...We have exact same issue where we need to kickoff workflow for readonly users with some other user's token which is getting expired as the fake user never logs in. Can we increase timeout of spusertoken to 6 months for specific user?Amit Lohogaonkar Sharepointerhttps://www.blogger.com/profile/13571670068586762663noreply@blogger.com