From c741e353b3760d3f2ce678765638e5080a3b415c Mon Sep 17 00:00:00 2001 From: Roman Flowers Date: Wed, 27 Sep 2023 11:23:26 -0500 Subject: [PATCH 1/4] ACP2E-2419: Document the updated behavior of isEmailAvailable endpoint in 2.4.7-b1 --- .../development/backward-incompatible-changes/highlights.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/pages/development/backward-incompatible-changes/highlights.md b/src/pages/development/backward-incompatible-changes/highlights.md index fb68697ae..b28074f85 100644 --- a/src/pages/development/backward-incompatible-changes/highlights.md +++ b/src/pages/development/backward-incompatible-changes/highlights.md @@ -57,7 +57,9 @@ The following module is affected by this change: ### `isEmailAvailable` API -The default behavior of the [`isEmailAvailable`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/is-email-available/) GraphQL query and ([`V1/customers/isEmailAvailable`](https://adobe-commerce.redoc.ly/2.4.6-admin/tag/customersisEmailAvailable/#operation/PostV1CustomersIsEmailAvailable)) REST endpoint has changed. By default, the API now always returns `false`. Merchants can enable the original behavior, which is to return `true` if the email does not exist in the database and `false` if it exists. +The default behavior of the [`isEmailAvailable`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/is-email-available/) GraphQL query and ([`V1/customers/isEmailAvailable`](https://adobe-commerce.redoc.ly/2.4.6-admin/tag/customersisEmailAvailable/#operation/PostV1CustomersIsEmailAvailable)) REST endpoint has changed. By default, the API now always returns `true` regardless of provided email address. +The new default behaviour also affects the checkout workflow for guests that do not realize they already have an account. Previously, by default, guests that do not realize they already have an account was prompted to sign in after entering their email address at the checkout page. Now, by default, guests are not offered to sing in even if they entered an email that is already belongs to an existing registered customer account. +By setting the "Enable Guest Checkout Login" configuration option located at "Config > Sales > Checkout" to "Yes", merchants can enable the original behavior, which is to return `true` if the email does not exist in the database and `false` if it exists, and prompting guest users to sign in during the checkout if their email already belongs to a registered customer account. Setting this option to yes, however, comes at the cost of exposing information to unauthenticated users. ## 2.4.6 From 7301209bdc51a97c912ba8b7669c618205fbe352 Mon Sep 17 00:00:00 2001 From: Thiaramus Date: Wed, 27 Sep 2023 15:28:59 -0500 Subject: [PATCH 2/4] Apply suggestions from code review Co-authored-by: Kevin Harper --- .../development/backward-incompatible-changes/highlights.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/development/backward-incompatible-changes/highlights.md b/src/pages/development/backward-incompatible-changes/highlights.md index b28074f85..7aeb2f4b1 100644 --- a/src/pages/development/backward-incompatible-changes/highlights.md +++ b/src/pages/development/backward-incompatible-changes/highlights.md @@ -57,8 +57,8 @@ The following module is affected by this change: ### `isEmailAvailable` API -The default behavior of the [`isEmailAvailable`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/is-email-available/) GraphQL query and ([`V1/customers/isEmailAvailable`](https://adobe-commerce.redoc.ly/2.4.6-admin/tag/customersisEmailAvailable/#operation/PostV1CustomersIsEmailAvailable)) REST endpoint has changed. By default, the API now always returns `true` regardless of provided email address. -The new default behaviour also affects the checkout workflow for guests that do not realize they already have an account. Previously, by default, guests that do not realize they already have an account was prompted to sign in after entering their email address at the checkout page. Now, by default, guests are not offered to sing in even if they entered an email that is already belongs to an existing registered customer account. +The default behavior of the [`isEmailAvailable`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/is-email-available/) GraphQL query and ([`V1/customers/isEmailAvailable`](https://adobe-commerce.redoc.ly/2.4.6-admin/tag/customersisEmailAvailable/#operation/PostV1CustomersIsEmailAvailable)) REST endpoint has changed. By default, the API now always returns `true`. +The new default behaviour also affects the checkout workflow for guests that do not realize they already have an account. Previously, by default, when a guest supplied an email address that matched an existing customer account, they were prompted to sign in. Now, they are no longer prompted to sign in. By setting the "Enable Guest Checkout Login" configuration option located at "Config > Sales > Checkout" to "Yes", merchants can enable the original behavior, which is to return `true` if the email does not exist in the database and `false` if it exists, and prompting guest users to sign in during the checkout if their email already belongs to a registered customer account. Setting this option to yes, however, comes at the cost of exposing information to unauthenticated users. ## 2.4.6 From 075af22feb66c9e8f243803664c09c748ea83df2 Mon Sep 17 00:00:00 2001 From: Roman Flowers Date: Wed, 27 Sep 2023 15:31:04 -0500 Subject: [PATCH 3/4] ACP2E-2419: Document the updated behavior of isEmailAvailable endpoint in 2.4.7-b1 --- .../development/backward-incompatible-changes/highlights.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/pages/development/backward-incompatible-changes/highlights.md b/src/pages/development/backward-incompatible-changes/highlights.md index 7aeb2f4b1..a6741fd06 100644 --- a/src/pages/development/backward-incompatible-changes/highlights.md +++ b/src/pages/development/backward-incompatible-changes/highlights.md @@ -59,8 +59,7 @@ The following module is affected by this change: The default behavior of the [`isEmailAvailable`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/is-email-available/) GraphQL query and ([`V1/customers/isEmailAvailable`](https://adobe-commerce.redoc.ly/2.4.6-admin/tag/customersisEmailAvailable/#operation/PostV1CustomersIsEmailAvailable)) REST endpoint has changed. By default, the API now always returns `true`. The new default behaviour also affects the checkout workflow for guests that do not realize they already have an account. Previously, by default, when a guest supplied an email address that matched an existing customer account, they were prompted to sign in. Now, they are no longer prompted to sign in. -By setting the "Enable Guest Checkout Login" configuration option located at "Config > Sales > Checkout" to "Yes", merchants can enable the original behavior, which is to return `true` if the email does not exist in the database and `false` if it exists, and prompting guest users to sign in during the checkout if their email already belongs to a registered customer account. Setting this option to yes, however, comes at the cost of exposing information to unauthenticated users. - +Merchants can restore the original default behavior of the `isEmailAvailable` API and checkout flow by setting the **Stores > Configuration > Sales > Checkout > Enable Guest Checkout Login field** to **Yes**. However, doing this can expose customer information to unauthenticated users. ## 2.4.6 The following major backward-incompatible changes were introduced in the 2.4.6 Adobe Commerce and Magento Open Source releases: From 36f15aa34d0c94028392f7bb88784cc999d9a4a9 Mon Sep 17 00:00:00 2001 From: Thiaramus Date: Wed, 27 Sep 2023 20:16:24 -0500 Subject: [PATCH 4/4] Update src/pages/development/backward-incompatible-changes/highlights.md Co-authored-by: Kevin Harper --- .../development/backward-incompatible-changes/highlights.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/pages/development/backward-incompatible-changes/highlights.md b/src/pages/development/backward-incompatible-changes/highlights.md index a6741fd06..1cf82d63d 100644 --- a/src/pages/development/backward-incompatible-changes/highlights.md +++ b/src/pages/development/backward-incompatible-changes/highlights.md @@ -59,7 +59,9 @@ The following module is affected by this change: The default behavior of the [`isEmailAvailable`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/is-email-available/) GraphQL query and ([`V1/customers/isEmailAvailable`](https://adobe-commerce.redoc.ly/2.4.6-admin/tag/customersisEmailAvailable/#operation/PostV1CustomersIsEmailAvailable)) REST endpoint has changed. By default, the API now always returns `true`. The new default behaviour also affects the checkout workflow for guests that do not realize they already have an account. Previously, by default, when a guest supplied an email address that matched an existing customer account, they were prompted to sign in. Now, they are no longer prompted to sign in. + Merchants can restore the original default behavior of the `isEmailAvailable` API and checkout flow by setting the **Stores > Configuration > Sales > Checkout > Enable Guest Checkout Login field** to **Yes**. However, doing this can expose customer information to unauthenticated users. + ## 2.4.6 The following major backward-incompatible changes were introduced in the 2.4.6 Adobe Commerce and Magento Open Source releases: