App was read-only, now is read/write. New access tokens aren't getting generated


#1

Hi,

My app was read-only, and many users authenticated.

I’ve since upgraded my app to read/write.

I’m using reverse auth from iOS to my backend.

When new users authenticate via iOS, they appear to be correctly authenticated for read/write access.

However, when legacy users authenticate via iOS, they do not appear to be generating new access tokens. Their legacy access tokens are still read-only.

I want users to be upgraded to read-write, and for new access tokens to be generated.

What’s the best way to handle this?

I don’t want to reset my consumer key/secret as it’s already baked into our iOS app. Is there a way to force the legacy access token to expire?

Thanks!