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

Make manual API calls with a session easy #39

Open
rishabhpoddar opened this issue Sep 29, 2020 · 2 comments
Open

Make manual API calls with a session easy #39

rishabhpoddar opened this issue Sep 29, 2020 · 2 comments

Comments

@rishabhpoddar
Copy link
Contributor

Right now, the developer has to set the tokens manually in Postman, and it can be difficult to know which those cookies are, and how to use them. Plus they keep changing over time.

Perhaps have a flag in the SDK that will enable them switch to a different mode of sessions where it's just one long lived token in the header which is mapped to the actual access / refresh tokens that the API expects.

@rishabhpoddar
Copy link
Contributor Author

In the init function of the various SDKs, have a boolean like isDev (default is false). If this is true & the user-agent is that of Postman, then, for an API that uses getSession:

  • Should not need to check if idRefreshToken is available.
  • Use the sAccessToken without verifying it.

We should also have a page in the docs for "Testing with Postman"
This will allow users to keep using one access token forever, in dev mode.

@rishabhpoddar
Copy link
Contributor Author

Another solution is to recommend the use of https://chrome.google.com/webstore/detail/postman-interceptor/aicmkgpgakddgnaphhhpliifpcfhicfo?hl=en

This auto adds cookies from the browser into postman.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant