Glydric
commented
3 months ago Correcting myself the problem is not about the two methods but is about using encode function, just don't use it and instead use toJson(), so use the following implementation
final cognitoPlugin = Amplify.Auth.getPlugin(AmplifyAuthCognito.pluginKey);
final result = await cognitoPlugin.fetchAuthSession();
final token = result.userPoolTokensResult.value.accessToken.toJson();the token then can be used to sign any request (I can now verify in the backend)
Jordan-Nelson
Description
I was developing an application in dart when I found out that the jwt value i was getting printing directly
let ses = await Amplify.Auth.fetchAuthSession() safePrint(ses);is different that the one obtained usingfinal tokens = ses.toJson()["userPoolTokens"] as CognitoUserPoolTokens; safePrint(tokens.accessToken.encode().toString());that should be used to extract the user pool token.I found out that the signature is equal, but using the second method it was someway reformatting the token and obtain a different base 64 value. that is instead wrong Indeed the first can be verified with jwt.io, while the latter is impossible to verify. This is a real problem as I seen from previous issues that I'm not the only one that founds out this problem. but maybe I just discovered this difference. I just discovered this on an iPhone 15 with ios 17.5, build using flutter 3.19.5 and dart 3.3.3 on macos 14.5
Categories
Steps to Reproduce
let ses = await Amplify.Auth.fetchAuthSession() safePrint(ses); // Correct accessToken jwt final tokens = ses.toJson()["userPoolTokens"] as CognitoUserPoolTokens; safePrint(tokens.accessToken.encode().toString()); // Wrong accessToken jwt
Screenshots
No response
Platforms
Flutter Version
3.19.5
Amplify Flutter Version
2.1.0
Deployment Method
Custom Pipeline
Schema
No response