AWSCredentialProvider is not being called when a operation fails with 403?

[jamesrusso]

I have a custom AWSCredentialProvider which accesses a web service to obtain a session identity using assume role. This identity is used in SQS client. However, when this role expires and the next time the SQS operations happens it returns 403 without consulting with the AWSCredentialProvider to get a new credential? I was under the impression that auth failures would re-call the provider to attempt to get new credentials?

[jamesrusso]

It seems to me, that if the expiration is not included in the token the refresh will never happen. So it's due to failure, but only due to getting close to expiration