Website restriction -> Private Sale: Login only, preventing registration on API as Admin

[ghezelbash]

Preconditions and environment

• Magento version: 2.4.5-p2 commerce
• Go to Stores > Configuration > General > General > Website Restrictions, set Access Restriction (general/restriction/is_active) to 'Yes' and set Restriction Mode (general/restriction/mode) to Private Sale: Login Only
• Create an admin integration token

Steps to reproduce

1. Go to Stores > Configuration > General > General > Website Restrictions
2. Set Access Restriction (general/restriction/is_active) to 'Yes' and set Restriction Mode (general/restriction/mode) to Private Sale: Login Only
3. Clear the config cache
4. Create an admin integration token from System > Integrations
5. Send a REST api POST request to /rest/V1/customers to create a customer and include admin integration token as Bearer token as Autorization

Expected result

Since admins can create custumers in Admin area when website restrictions is on, then they should have the ability to create customers via API. Expected: Customer created. (Registration working when the requester is an admin user)

Actual result

API raises a 400 bad request response saying: "Can not register new customer due to restrictions are enabled."

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @ghezelbash. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @ghezelbash,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance with EE edition and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

• Go to Stores > Configuration > General > General > Website Restrictions
• Set Access Restriction (general/restriction/is_active) to 'Yes' and set Restriction Mode (general/restriction/mode) to Private Sale: Login Only
• Clear the config cache
• Create an admin integration token from System > Integrations
• Send a REST api POST request to /rest/V1/customers to create a customer and include admin integration token as Bearer token as Autorization

We are not able to customer using REST API's but we are able to create the customer form the admin side .

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-9613 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.