Use a new callback route named "$slug/oauth/callback/{provider}" which already contains the panel slug. This should simplify the logic since the CSRF protection is already handled by Socialite itself. In addition, this should resolve certain issues where providers would not send a state query to the callback url.
Use a new callback route named
"$slug/oauth/callback/{provider}"which already contains the panel slug. This should simplify the logic since the CSRF protection is already handled by Socialite itself. In addition, this should resolve certain issues where providers would not send a state query to the callback url.