Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AmazonChimeSDK uses expired chime credentials after providing new credentials. #686

Open
aparna-tati-simformsolutions opened this issue Jul 30, 2024 · 0 comments
Labels
question Further information is requested

Comments

@aparna-tati-simformsolutions

Describe the bug
AmazonChimeSDK uses expired chime credentials even after providing the new chime credentials.

To Reproduce
Steps to reproduce the behavior:

  1. We have put 15 min timeout for chime credentials expire time from backend.
  2. After expiring the credentials we will taking new credentials and trying to intialise the SDK again.
  3. It will give The Security token an expired exception in getSessionEndPoint() function and we have debugged your SDK we have seen, the SDK is still using expired credentials even when we are passing new credentials.

Expected behavior
After the chime credentials expire and are initialised with new credentials, The SDK must need to use new chime credentials instead of expired credentials.

ChimeSDK Version
I am using 'AWSChimeSDKMessaging', '~> 2.36.3' this version

@ziyiz-amzn ziyiz-amzn added the question Further information is requested label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants