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
There are security issues with increasing the age of a JSON token as it is a key to access the API. They are meant to be short lived I think.
Something I read mentioned having a refresh token that you could use to request an issue of another auth token, but I'm not sure how that would work if you left a site for weeks before coming back to it.
This will work for cookie based auth like on zume or DT, but PG uses JSON tokens, so we > would need to come up with another way of extending the life of those Originally posted by @squigglybob in #2537 (comment)
The text was updated successfully, but these errors were encountered:
There are security issues with increasing the age of a JSON token as it is a key to access the API. They are meant to be short lived I think.
Something I read mentioned having a refresh token that you could use to request an issue of another auth token, but I'm not sure how that would work if you left a site for weeks before coming back to it.
The text was updated successfully, but these errors were encountered: