From 5c3223d8feee748a9764cade172f52d53ced5511 Mon Sep 17 00:00:00 2001 From: Damodar Lohani Date: Thu, 24 Jun 2021 11:52:08 +0545 Subject: [PATCH 1/3] update oAuth2 session doc --- docs/references/account/create-session-oauth2.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/references/account/create-session-oauth2.md b/docs/references/account/create-session-oauth2.md index fb6fa41b27..0f905e01b0 100644 --- a/docs/references/account/create-session-oauth2.md +++ b/docs/references/account/create-session-oauth2.md @@ -1 +1,3 @@ -Allow the user to login to their account using the OAuth2 provider of their choice. Each OAuth2 provider should be enabled from the Appwrite console first. Use the success and failure arguments to provide a redirect URL's back to your app when login is completed. \ No newline at end of file +Allow the user to login to their account using the OAuth2 provider of their choice. Each OAuth2 provider should be enabled from the Appwrite console first. Use the success and failure arguments to provide a redirect URL's back to your app when login is completed. + +If there is already an active session, the new account details is attached to the same account that has the active session. If there is no active sessions, it will look for the user with the same email address as the email received from OAuth2 provider and attach new session to the existing user if found or create a new user if the email doesn't exist in the database. \ No newline at end of file From 598a187a289c2117be9084368c0320fd0625f1be Mon Sep 17 00:00:00 2001 From: Damodar Lohani Date: Fri, 25 Jun 2021 12:32:43 +0545 Subject: [PATCH 2/3] Update docs/references/account/create-session-oauth2.md Co-authored-by: Bradley Schofield --- docs/references/account/create-session-oauth2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/references/account/create-session-oauth2.md b/docs/references/account/create-session-oauth2.md index 0f905e01b0..1c0d63b590 100644 --- a/docs/references/account/create-session-oauth2.md +++ b/docs/references/account/create-session-oauth2.md @@ -1,3 +1,3 @@ Allow the user to login to their account using the OAuth2 provider of their choice. Each OAuth2 provider should be enabled from the Appwrite console first. Use the success and failure arguments to provide a redirect URL's back to your app when login is completed. -If there is already an active session, the new account details is attached to the same account that has the active session. If there is no active sessions, it will look for the user with the same email address as the email received from OAuth2 provider and attach new session to the existing user if found or create a new user if the email doesn't exist in the database. \ No newline at end of file +If there is already an active session, the new account details is attached to the same account that already has the active session. If there are no active sessions, it will look for the user with the same email address as the email received from OAuth2 provider and attach the new session to the existing user if found however it will create a new user if the email doesn't exist in the database. From 64b2fc8056bb212344fe0bd0e13ed43d7060ebaf Mon Sep 17 00:00:00 2001 From: Damodar Lohani Date: Mon, 28 Jun 2021 13:18:44 +0545 Subject: [PATCH 3/3] Update docs/references/account/create-session-oauth2.md Co-authored-by: Eldad A. Fux --- docs/references/account/create-session-oauth2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/references/account/create-session-oauth2.md b/docs/references/account/create-session-oauth2.md index 1c0d63b590..e909899371 100644 --- a/docs/references/account/create-session-oauth2.md +++ b/docs/references/account/create-session-oauth2.md @@ -1,3 +1,3 @@ Allow the user to login to their account using the OAuth2 provider of their choice. Each OAuth2 provider should be enabled from the Appwrite console first. Use the success and failure arguments to provide a redirect URL's back to your app when login is completed. -If there is already an active session, the new account details is attached to the same account that already has the active session. If there are no active sessions, it will look for the user with the same email address as the email received from OAuth2 provider and attach the new session to the existing user if found however it will create a new user if the email doesn't exist in the database. +If there is already an active session, the new session will be attached to the logged-in account. If there are no active sessions, the server will attempt to look for a user with the same email address as the email received from the OAuth2 provider and attach the new session to the existing user. If no matching user is found - the server will create a new user..