-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add custom refresh handlers for custom federated identities. #624
Comments
I feel like I'm doing this wrong anyway :) I'll investigate more and close this if I am doing something wrong. |
Okay now that I have gone through everything I possibly can. I found out that I was indeed performing the federated sign in incorrectly. This line:
Should be this line:
But it brings me right back to the same issue.
So, I'd like to continue or begin the discussion about allowing developers to provide their own refresh handlers. Without a refresh handler the local storage gets cleared on every page load, and would likely cease to function after 5 minutes if the page was left open that long. |
Also, see this PR #665 which fixes an issue with providing the identity_id to the developer token. |
I think this is already provided, (Maybe you forgot to close this one already, but) you have to return a promise like this. Auth.configure({
@nidsharm I think you can close this one. |
Yup, I added the ability to provide custom refresh handlers in the referenced PR. Closing! |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
I'd like to request a feature.
What is the current behavior?
I'm using
$cognito_client->getOpenIdTokenForDeveloperIdentity([/* custom things here */])
in php to get a developer token which I then pass into AWS Amplify by issuing the following:On the first request this works great! I get logged in and all is great. The second request I get
When this message is displayed the credentials are cleared and reloaded on the next page refresh.
I'm wondering if there is a way to provide my own custom refresh handler, or if you'd be interested in a PR where I explore this functionality.
Something along the lines of the following
The text was updated successfully, but these errors were encountered: