Skip to content
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

aws-export.js responseType #3924

Closed
saaniaki opened this issue Aug 26, 2019 · 3 comments
Closed

aws-export.js responseType #3924

saaniaki opened this issue Aug 26, 2019 · 3 comments
Assignees
Labels
Auth Related to Auth components/category

Comments

@saaniaki
Copy link

Describe the bug
By adding or updating "auth" using amplify and setting the OAuth flow to "implicit" option, and pushing it using "amplify push", aws-export.js file would be generated with a wrong parameter in the responseType of oauth section. This parameter can only have values of "code" or "token", but amplify cli would put "implicit" as the value, causing the oauth endpoints to return 400 response code.

@sammartinez sammartinez transferred this issue from aws-amplify/amplify-js Aug 27, 2019
@sammartinez sammartinez transferred this issue from aws-amplify/amplify-cli Aug 27, 2019
@sammartinez sammartinez added Auth Related to Auth components/category to-be-reproduced Used in order for Amplify to reproduce said issue labels Aug 27, 2019
@ashika01 ashika01 self-assigned this Oct 16, 2019
@ashika01 ashika01 removed the to-be-reproduced Used in order for Amplify to reproduce said issue label Oct 22, 2019
@ashika01
Copy link
Contributor

@saaniaki : Are you still having this issue? With the current version of amply-cli, aws-export.js has "responseType": "token". Could you verify with a newer version?

@saaniaki
Copy link
Author

Amplify Cli @1.8.1 was what I was using. Currently we have migrated from Cognito so I can't confirm if the bug still exists on the latest version or not.

@github-actions
Copy link

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 *-help channels or Discussions for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Auth Related to Auth components/category
Projects
None yet
Development

No branches or pull requests

3 participants