You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: