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

Add Authorization header to GraphQL operations #696

Closed
hassankhan opened this issue Apr 19, 2018 · 2 comments
Closed

Add Authorization header to GraphQL operations #696

hassankhan opened this issue Apr 19, 2018 · 2 comments
Labels
feature-request Request a new feature GraphQL Related to GraphQL API issues

Comments

@hassankhan
Copy link

Feature Request

What is the current behavior?

Currently if a user uses a GraphQL endpoint, aws-amplify does not seem to apply any headers that would usually be on a request made from API.post().

What is the expected behavior?

It would be nice to be able to specify that the GraphQL endpoint is also AWS_IAM authorized.


Amplify v0.3.0

@mlabieniec mlabieniec added feature-request Request a new feature GraphQL Related to GraphQL API issues labels Apr 21, 2018
@honkskillet
Copy link

Yes. I second this. Working with AWS Amplify and AppSync using IAM auth. The context identity object in AppSync is from Congito Identities (not User Pool) and does not have any user information. I would love to just be able to pass the authenticated user's JWT as a header.

@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 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request a new feature GraphQL Related to GraphQL API issues
Projects
None yet
Development

No branches or pull requests

4 participants