-
Notifications
You must be signed in to change notification settings - Fork 9.4k
magento/magento2#: Remove oauthUserContext from app/code/Magento/GraphQl/etc/graphql/di.xml #27373
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
magento/magento2#: Remove oauthUserContext from app/code/Magento/GraphQl/etc/graphql/di.xml #27373
Conversation
Failed Functional tests are not tie to the PR changes. |
b8d9aba
to
e601c74
Compare
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.
Hello @atwixfirster, thank you for your contribution!
Due to Magento Definition of Done the changes should be covered by automated tests. Could you please cover this case by API functional test?
Thank you!
5c57d52
to
7361a79
Compare
done Thank you, @dmytro-ch |
Hi @atwixfirster, thank you for your contribution! |
Hi @atwixfirster. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
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.
Please see comment #28040 (comment)
Could you please remove oauthUserContext
from the ce/app/code/Magento/GraphQl/etc/graphql/di.xml:18
instead.
…thorization\Model\CompositeUserContext in GraphQl operations
429aad8
to
b96c8e9
Compare
done |
Hi @lenaorobei, thank you for the review.
|
…/Magento/GraphQl/etc/graphql/di.xml #27373
Hi @atwixfirster, thank you for your contribution! |
@danielrenaud @lenaorobei @paliarush Will this PR break the staging functionality in GraphQL? |
Description (*)
Issue:
With an active customer's cookies and empty Authorization token GraphQl uses cookies to retrieve a type of user and it's ID.
That's incorrect behavior because GraphQl should use an
Authorization token
ONLY to retrieve a type of user and it's ID.Technical details:
Magento_Customer/etc/graphql/di.xml
adds customerSessionUserContext into\Magento\Authorization\Model\CompositeUserContext
. It allows to retrieves a customer ID from the session (cookies) wihtin GraphQl operations.Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Preconditions:
Magento_UpwardConnector
Actual result: guest sees a product which customer has been added into shopping cart. Current quote as a masked quote ID of registered customer.
Expected result: a new guest quote has been created after customer's logout.
Questions or comments
Contribution checklist (*)