Hi @anders.
Unfortunately, the only way as of now would be to ask the users to authorize again, because of two reasons:
The refresh tokens obtained with the pre-OIDC-Conformant pipeline are not compatible with the OIDC-Conformant pipeline. The old refresh tokens are not associated with any “grant”, i.e. the user consenting (implicitly or explicitly) Auth0 to issue a token to the application to access the API (audience) on behalf of the user.
You cannot obtain a new refresh token from an old refresh token or id token.
I’m sorry for the added friction on this, but there are too many changes under the hood in the pipelines to make the transition more seamlessly.
Having all our users being forced to re-authenticate in our app will probably result in a drop in usage/sessions.
Which potentially has an impact on our bottom line.
What are your estimates of this drop in usage?
For now we will be relying on the /delegate endpoint to refresh pre-OIDC issued ID tokens.
Sorry for such huge delay in response! We’re doing our best in providing you with best developer support experience out there, but sometimes our bandwidth is not enough comparing to the number of incoming questions.
Wanted to reach out to know if you still require further assistance?