In `fetchAuthSession()`, `token` and `subs` are undefined, whereas in Amplify version 5, they are available. about amplify-js HOT 3 CLOSED

@TitusEfferian Glad to hear you got it working! Thank you for your feedback on the documentation structure, we will take that into consideration.

from amplify-js.

Hello, @TitusEfferian 👋. It looks like you are missing the tokenProvider for your custom auth flow. You'll need to import the TokenProvider from aws-amplify/auth and use that within your Amplify.configure() call like seen here. Doing so should provide you with both the tokens and userSub.

Let me know if that doesn't resolve the issue for you!

from amplify-js.

Hi @cwomack, thanks for the response. Yes, it's now working as expected. However, as a user who has transitioned from Amplify version 5 to version 6, I feel that the documentation could be improved. In the previous version (v5), performing this action would automatically return tokens:

// get data from auth0
const sync = await getIdTokenClaims();

const cred = await Auth.federatedSignIn(
  "my auth0 domain",
  {
    token: sync?.__raw || "",
    expires_at: (sync?.exp || 0) * 1000,
  },
  {
    name: sync?.name || "",
    email: sync?.email || "",
    picture: sync?.picture || "",
    sub: sync?.sub || "",
   ...add another additional data here
  },
);

const user = await Auth.currentAuthenticatedUser();
// output
{
  "id": "my id",
  "token": "my token"
}

In version 6, I need to undertake additional processes to achieve the same expected result, as you mentioned:

You'll need to import the TokenProvider from aws-amplify/auth and use that within your Amplify.configure() call like seen here. Doing so should provide you with both the tokens and userSub.

This is just my proposal for improvement: perhaps this section could be moved after the Identity Pool Federation section, as they are still related. I didn't realize this additional step was necessary.

from amplify-js.