Closed aniruddhaad closed 2 years ago
Ok. If anyone still having this issue. I think solution is just to truncate the temporary aws-tokens i.e. SimpleTokenStorage file. Everytime you run the code just truncate the file. I don't think contents of this file are rechecked for if its still valid or not. TODO: Perhaps a simple check in SimpleTokenStorage class/function would solve the issue without doing any further actions to be taken outside the class. Please correct me if I am wrong.
Hi there, I run to the same problem - will think of something and will implement it. My situation however is a little bit special - long running proces which uses only one instance of a client
I don't think contents of this file are rechecked for if its still valid or not.
This is not true. The file is checked whenever a fresh credentials are made
Hi there, I run to the same problem - will think of something and will implement it. My situation however is a little bit special - long running proces which uses only one instance of a client
I don't think contents of this file are rechecked for if its still valid or not.
This is not true. The file is checked whenever a fresh credentials are made
I end up creating different temporary files per user so that they don't cause problems with any other accounts as effect of multiple instance of same script running.
Well - the TokenStorage accepts configuration. The user can specify different storage files for different workers Kind Regards, Lyubomir Slavilov
On Mon, Jan 10, 2022 at 9:18 AM aniruddhaad @.***> wrote:
Hi there, I run to the same problem - will think of something and will implement it. My situation however is a little bit special - long running proces which uses only one instance of a client
I don't think contents of this file are rechecked for if its still valid or not.
This is not true. The file is checked whenever a fresh credentials are made
I end up creating different temporary files per user so that they don't cause problems with any other accounts as effect of multiple instance of same script running.
— Reply to this email directly, view it on GitHub https://github.com/double-break/spapi-php/issues/41#issuecomment-1008596771, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEGJUIBVIDPHQTSWGHMYOTUVKB3RANCNFSM5E5UXTYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message ID: @.***>
It randomly gives me "unauthorized error" "The security token included in the request is expired".
I observed that, in the Credentials.php there is getLWAToken() function which does the job of refreshing the token however it returns access token only.
I am not sure if we have to manually make some calls to refresh the token or the library does that for me?
Anyone knows?