cwomack
commented
4 weeks ago Hello, @Unemployed and thank you for opening this issue. I'm marking this as a feature request at this time due to the cognitoUserPoolsTokenProvider being a singleton that is not connected to Amplify.configure(). This means that manual updates are needed every time when you're looking to change your config for Auth. The way you're currently working around this by calling Amplify.configure again as needed to update the auth config used by the token provider is the only way to do this right now.
I'll review this with the team to see if there's a way we can resolve this and follow up with any additional questions we may have.
Unemployed
mariasemionova
Before opening, please confirm:
JavaScript Framework
React
Amplify APIs
Authentication
Amplify Version
v6
Amplify Categories
auth, storage
Backend
None
Environment information
Describe the bug
cognitoUserPoolsTokenProviderdoes not respect Cognito changes toAmplify.configure(...)after initial load, and writes to local storage using outdated config keys. Requires a call tocognitoUserPoolsTokenProvider.authTokenStore.setAuthConfigto update the config.From:
import { cognitoUserPoolsTokenProvider } from "aws-amplify/auth/cognito";Expected behavior
I expected
<Authenticator>UI component would always persist token details using the last set amplify config, even if the component is re-rendered.Reproduction steps
Using SPA, page is not refreshed until step 7:
Amplify.configure(config1);<Authenticator>componentsignOutfromuseAuthenticator((x) => [x.signOut]);Amplify.configure(config2);<Authenticator>UI componentCognitoIdentityServiceProvider.OLD_CLIENT_ID.x.clockDrift...Code Snippet
Log output
aws-exports.js
No response
Manual configuration
Config1:
Config2:
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
Update config when clicking either radio button:
Auth flow is
USER_SRP_AUTHfor both configs.