We have a case where the scope that is being requested might be different from the one that is cached, but the oauth flow always use the cached version, so the new scope is never picked up.
I've added a flag to the client.authorize() method that explicitly tells the oauth flow to ignore the cache. It defaults to false so existing calls shouldn't be affected. Does that make sense? Is there a better way to accomplish this?
We have a case where the
scope
that is being requested might be different from the one that is cached, but the oauth flow always use the cached version, so the new scope is never picked up.I've added a flag to the
client.authorize()
method that explicitly tells the oauth flow to ignore the cache. It defaults to false so existing calls shouldn't be affected. Does that make sense? Is there a better way to accomplish this?