Dedicated to the Hydrogen framework, headless commerce, and building custom storefronts using the Storefront API.
Hello,
We have a website and related shopify store for the business. Currently the users log in to our website and seamlessly access the shopify store for the purchase using multipass.
We want to replace multipass with Customer Account API. It looks like Shopify's new Customer account experience is required to use the Customer Account API, and Shopify customers should log in using a one-time, six-digit verification code sent to their email (To receive the code required to authenticate and to get the access token for Customer Account API).
We want to keep the customer login part at our website itself (without the password less verification code) and use the Customer Account API to seamlessly access the store and website replacing multipass.
Please let me know if this is possible and how we would be able to implement this.
Many thanks
+1 for this. I have an app with its own user management and authentication. Multipass works perfectly for my use-case when it comes to actions like creating a cart, however I would love to use the graphQL @inContext directive to contextualize my Storefront API requests to a specific customer/company location. The multipass customerAccessToken does not seem to work in the @inContext directive, and I can't seem to find a way to create a customerAccessToken from the new Customer Accounts API without forcing the user to sign in through Shopify (not what I want since I have my own user management and my users should not be interfacing with Shopify).
Is there no way – even with the client_id and secret – to tell the Customer Accounts API "Hey, this user is logged in within my system. I have the secret key for admin access. Please issue me a token"? Feels like this would be a pretty common use case for headless apps that are using Shopify as more of a CMS than a customer interface.