Long lived tokens for testing purposes
Our challenge is with our test and verification setup: we have 4 stages of pre-production environments and every environment runs CI (Jenkins) with full tests each night and relevant tests with each code push. With this setup it is very challenging to share and update shared refresh tokens.
We would like long lived tokens (access and/or refresh) for testing purposes only.
Other services we work with have been able to change settings on app/client id level.
1
vote
Johan Friedrichsen
shared this idea