-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 Feature: OAuth2 allow for additional query parameters #3552
Labels
enhancement
New feature or request
Comments
Right now I am solving this by hitting my logout window directly for the next login, which is not ideal having to pop user over to new window. const deleteSessions = async () => {
if (!account) return null;
try {
await account.deleteSessions();
setUser(null);
setSessions(null);
const wnd = window.open("https://codingcatdev.us.auth0.com/v2/logout");
setTimeout(() => {
wnd?.close();
}, 1000);
} catch (error) {
throw error;
}
}; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🔖 Feature description
When calling
createOAuth2Session
there should be a way to pass in additional parameters. An example would be when trying to callauth0
, I want to be able to pass inprompt=login
to forcibly have the user login every time they call login. Currently when calling the authorization endpoint Auth0 sees that their is a user already active and automatically logged in.🎤 Pitch
I would like to change
createOAuth2Session(provider: string, success?: string, failure?: string, scopes?: string[]): void | URL;
in the sdk to take in a new parameter additionalQuery.
createOAuth2Session(provider: string, success?: string, failure?: string, scopes?: string[], scopes?: string[], additionalQueries?: string[]): void | URL;
This would require a change within Appwrite's internals here
appwrite/src/Appwrite/Auth/OAuth2.php
Line 41 in fb5805a
to include the
Then you can make overrides like in Auth0
appwrite/src/Appwrite/Auth/OAuth2/Auth0.php
Line 43 in fb5805a
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: