-
Notifications
You must be signed in to change notification settings - Fork 110
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
DEVDOCS-5274: [update] GQL Overview, clarify no multiple sign in support #2122
Conversation
If you're using the GraphQL Storefront API from a browser, for example, on top of your Stencil storefront, you can use the Customer Login mutation to sign in to a customer account with an email address and a password. This will set a session cookie in the browser, which will authenticate the customer account on future requests. | ||
|
||
<Callout type="info"> | ||
Customers cannot have multiple log-ins from different devices. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Customers cannot have multiple log-ins from different devices. | |
Note: A customer cannot be signed in to their account on multiple devices at the same time. |
@@ -222,6 +226,9 @@ mutation Login($email: String!, $pass: String!) { | |||
} | |||
} | |||
``` | |||
<Callout type="info"> | |||
NOTE: Customers are restricted from multiple logins from different devices. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NOTE: Customers are restricted from multiple logins from different devices. | |
Note: A customer cannot be signed in to their account on multiple devices at the same time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we say more about the default behavior here? does BC automatically sign them out of the old device when you run the customer login mutation for a session on a new device?
Successor branch is https://github.com/bigcommerce/docs/tree/DEVDOCS-5274. |
…rt (#10) <!-- Ticket number or summary of work --> # [DEVDOCS-5274] ## What changed? Document the fact that a customer can only be logged into one device at a time ## Release notes draft <!-- Provide an entry for the release notes using simple, conversational language. Don't be too technical. Explain how the change will benefit the merchant and link to the feature. Examples: * The newly-released [X feature] is now available to use. Now, you’ll be able to [perform Y action]. * We're happy to announce [X feature], which can help you [perform Y action]. * [X feature] helps you to create [Y response] using the [Z query parameter]. Now, you can deliver [ex, localized shopping experiences for your customers]. * Fixed a bug in the [X endpoint]. Now the [Y field] will appear when you click [Z option]. --> * ## Anything else? Old PR: bigcommerce/dev-docs#2122 ping {names} [DEVDOCS-5274]: https://bigcommercecloud.atlassian.net/browse/DEVDOCS-5274?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ --------- Co-authored-by: Sarah Riehl <sarah.riehl@bigcommerce.com> Co-authored-by: bc-andreadao <96258747+bc-andreadao@users.noreply.github.com>
DEVDOCS-5274
What changed?
Document the fact that a customer can only be logged into one device at a time
Release notes draft
Anything else?
ping {names}