Skip to content
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

Can not save an inactive Admin User that has no access tokens generated #16513

Closed
dpoltoratsky opened this issue Jul 3, 2018 · 3 comments
Closed
Assignees
Labels
Component: Integration Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@dpoltoratsky
Copy link

Preconditions

  1. Magento version 2.2.3
  2. An inactive Admin User that has no access tokens generated

Steps to reproduce

  1. Log in to Admin Panel
  2. Navigate to "System" -> "Permissions" -> "All Users"
  3. Click on the inactive Admin User
  4. Click "Save User"

Expected result

  1. The Admin User is successfully saved

Actual result

  1. The Admin User is not saved
  2. Following error message is shown:

This user has no tokens.

@magento-engcom-team
Copy link
Contributor

Hi @dpoltoratsky. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

@dpoltoratsky do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jul 3, 2018
@engcom-backlog-nickolas engcom-backlog-nickolas added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Component: Integration Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Jul 4, 2018
@engcom-backlog-nickolas
Copy link

Hello @dpoltoratsky, thank you for your report.
We've acknowledged the issue and added to our backlog.

@engcom-backlog-nickolas engcom-backlog-nickolas added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jul 4, 2018
@engcom-backlog-nickolas engcom-backlog-nickolas removed their assignment Jul 4, 2018
@ghost ghost assigned mage2pratik Apr 2, 2019
@magento-engcom-team
Copy link
Contributor

Hi @dpoltoratsky. Thank you for your report.
The issue has been fixed in #20772 by @mage2pratik in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.2 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Apr 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Integration Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

4 participants