Refreshing JWT Tokens misplaced in user pool authentication section
See original GitHub issueDescribe the bug
Refreshing JWT Tokens
section is misplaced in user pool federation section.
To Reproduce Steps to reproduce the behavior:
- Go to https://aws-amplify.github.io/docs/js/authentication#react-components
- Scroll to Refreshing JWT Tokens
Expected behavior
- Talking about AWS credentials in the context of Cognito User Pools authentication does not apply.
- This statement about automatic token refresh should be only in Cognito Identity Pool Federation as in https://aws-amplify.github.io/docs/js/authentication#token-refresh where Cognito does refresh tokens of Google/Facebook automatically to keep AWS credentials valid at all times.
Screenshots N/A
Additional context
- Related issue where user asking why Facebook/Google tokens returned in user pool idp attribute mapping are not refreshed, during Cognito user pool own id/access tokens are refreshed.
- User expected the above misplaced statement to mean that FB/Google tokens returned by attribute mapping (if any) would be refreshed as well.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Refresh token with JWT authentication in Node.js - Izertis
Refresh token : The refresh token is used to generate a new access token. Typically, if the access token has an expiration date,...
Read more >What Happens If Your JWT Is Stolen? - Okta Developer
What happens if a JSON Web Token is stolen or compromised? What are the security considerations you need to understand?
Read more >Using the refresh token - Amazon Cognito - AWS Documentation
Use the API or hosted UI to initiate authentication for refresh tokens. To use the refresh token to get new ID and access...
Read more >AWS Identity Token Refreshes But The Refresh Token is lost
I am writing a webpage that requires the user to be authenticated when trying to make requests to the server. In order to...
Read more >Macaroons as access and refresh tokens :: AM 7.2.0
Enable macaroons · In the AM admin UI, go to Realms > Realm Name > Services > OAuth2 Provider. · On the Core...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I get what you are saying, but you are viewing it very narrowly. I understand that identity federation is for authorizing access to AWS resources. When you use Federated Identities with a Cognito User Pool, the Cognito User Pool is a linked login (providing the Authentication piece). Have you used Federated Identities in conjunction with Cognito User Pools? The 2 are tightly integrated. Cognito User Pools is a Identity Provider for the Identity Pool.
For example, if I set up an IdentityPool, I pass in my Cognito User Pool as an identity provider (IdP). My authenticated CognitoUser assumes the Authenticated Role in my Identity Pool.
Anyhow, my question is specifically related to Identity Federation within Cognito User Pools (using LWA as an external identity provider for a Cognito User Pool). So, yes, it is not relevant to standalone Identity Pool Federation. I use a combination (as shown above). So, that could explain the confusion.
following up on this issue as it’s a year old. It looks like you originally linked to our old docs and auth has been re-organized here: https://docs.amplify.aws/lib/auth/advanced/q/platform/js.
Please open a new issue with feedback on this. Thank you