Customer does not keep authenticated when navigating from Catalyst storefront to Optimized One-Page Checkout

[Pedro-Silva-MM]

Describe the bug
Running a Catalyst application locally, logging in as a customer, adding items to the cart and proceeding to checkout even though the user was authenticated on the storefront the checkout prompts the user to log in.

To Reproduce
Steps to reproduce the behavior:

1. Run a Catalyst application locally
2. Log in as a customer
3. Add items to the cart
4. Go to checkout

Expected behavior
The customer should remain authenticated from storefront to checkout.

[bookernath]

Thanks for your report @Pedro-Silva-MM. This is being added very soon with an improvement to the GraphQL Storefront API which will persist the customer session through to the checkout.

In the meantime, if you require this functionality right now, you can look at the approach in this PR which uses the Customer Login API to do so: #715

This approach requires a Client Secret from an API account created directly in the BigCommerce Control Panel.

Once we release our new approach, this will become a feature of the GraphQL Storefront API and will not require any additional credentials.

I'll keep this issue open until we release our new feature.

[Pedro-Silva-MM]

Thank you =)

[smotlythomas]

We have the same issue, some updates about this ?

[jorgemoya]

#1262 should fix this issue but we're finalizing some details before we merge.

[jorgeserras]

#1262 should fix this issue but we're finalizing some details before we merge.

Any expected date for the merge?

[chanceaclark]

We have been delayed after testing some fixes for this functionality in our other environments. Still waiting on security review to release this further. Thanks for bearing with us on this!

[chanceaclark]

This should fixed in a Catalyst -> Checkout direction. We still need to implement some stuff, both in Catalyst and in checkout to support keeping logged in state in the other direction but I think we can consider this fixed for now.