Hi Ajinkya, The error code returned in case of an expired token indeed is "Access Denied" and needs to be corrected. A new session token can be retrieved by making another AssumeRole* call with "*DurationSeconds" *parameter set to the duration for which the token is needed *.* Thanks, Pritha On Tue, Mar 26, 2024 at 7:45 AM Ajinkya Deshpande < Ajinkya.Deshpande@veritas.com> wrote:

Dear Team,

I have a query regarding STS token refresh. In the case of CEPH, when a token expires and we attempt any operation, we receive an "*access denied*" error. However, with other S3 providers like Amazon, we receive the correct error code "*ExpiredToken.*" Is this discrepancy a known issue with CEPH , and if so, do we have plans to address it? Having "access denied" as the error code in the event of token expiry seems incorrect.

Given the above scenario, please let us know how token refresh can be handled with CEPH ?

*Ajinkya Deshpande*

Sr Software Engineer

NetBackup Engineering

Veritas Technologies LLC

Mobile: (7776835515)

Ajinkya.Deshpande@veritas.com

_______________________________________________ Dev mailing list -- dev@ceph.io To unsubscribe send an email to dev-leave@ceph.io