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
I like to ask how does next-auth officially support dynamic scope.
I.e. asking for the scope of an auth that is regularly needed, and ask for incremental scope when the feature calls for it.
For example, ask for "email" and "openid" when user sign in, but ask for "email send" and "email read" later when it's necessry.
I figured that the signIn call can pass ing extra scope. e.g. signIn(providerId, { callbackUrl }, { scope });
But for me (testing with azure-ad) the new scope and the refresh token is not stored in Account.
What is the official supported way of implementing dynamic scope? Thank you!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I like to ask how does next-auth officially support dynamic scope.
I.e. asking for the scope of an auth that is regularly needed, and ask for incremental scope when the feature calls for it.
For example, ask for "email" and "openid" when user sign in, but ask for "email send" and "email read" later when it's necessry.
I figured that the
signIn
call can pass ing extra scope. e.g.signIn(providerId, { callbackUrl }, { scope });
But for me (testing with azure-ad) the new scope and the refresh token is not stored in
Account
.What is the official supported way of implementing dynamic scope? Thank you!
Beta Was this translation helpful? Give feedback.
All reactions