REQUEST HELP - GraphQL Token Authentication with Configuration
Greetings,
Our team is currently facing issues with configuring the GraphQL API. We have successfully set up HTTPS, but are experiencing difficulties in switching from HTTPS to GraphQL.
Our current authentication process involves sending a header containing {"username":"username","password":"password"} to root.com/auth/token. From the response body, we retrieve the "access_token" and use it as a bearer token for root.com/graphql.
We then will use root.com/auth/refresh for "refresh_tokens"
We kindly request assistance with the API configuration.
-
Weifeng Yang can you send some screenshots of your existing HTTP connection? I'm a bit confused from your second to last sentence:
We then will use root.com/auth/refresh for "refresh_tokens"
It sounds like you would set this up as token based authentication, configure refresh token by getting a new access_token via /auth/token. I'm not sure how you would even have the additional /auth/refresh configured.
0 -
Thank you Tyler, for follow up.
We managed to get our connections working yesterday.
We were mainly confused on the configuration especially on the relative URL due to unclear bullet points.
Since we need to use root.com/graphql as a base URI, we had thought there were no way for us to use root.com/auth/token for relative url.0 -
Weifeng Yang did you end up just using the full url in the relative url field? So for the main base url, you used the /graphql full url, then refresh token relative url was the full root.com/auth url?
0
Please sign in to leave a comment.
Comments
3 comments