admin Password update.

[Gopaal3]

Preconditions and environment

• Magento version 2.4.4
• Anything else that would help a developer reproduce the bug

Steps to reproduce

• Customer put his credentials for login
• He got asked for 2fa auth, and he puts the code
• He gots redirected to a "change password page" (that actually has a lot of other fields). Admin changes his password, clicks "Save" button.

Expected result

• ✅ You should see the message that your password was changed
• ✅ You should be redirected to the home admin page (because your main flow was a log in flow, not the change password)

Actual result

• ✅ You should see the message that your password was changed
• ❌ You're still see the "change password" page, so you think that Magento asks you to change a password one more time

Additional information

No response

Release note

when i click save . it is not working

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.
• [ ] 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 @Gopaal3. 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.

[andrewbess]

Hello @Gopaal3 Thank you for your collaboration I tried to reproduce described problem on the Magento 2.4.4 It works great Could you please provide more information Looks like you have 3rd-party extension that can provoke the problem Thank you in advance.

[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]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://bae5c16dabaa786afe2c15e3e1dd0a5c.instances-prod.magento-community.engineering Admin access: https://bae5c16dabaa786afe2c15e3e1dd0a5c.instances-prod.magento-community.engineering/admin_9e09 Login: dad37f06 Password: 698771c7200a

[engcom-Bravo]

@andrewbess Thanks for your contribution and collaboration.

Hi @Gopaal3,

Thank you for reporting and collaboration.

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

Steps to reproduce

1.login admin 2.update password

We are able to update the password successfully.

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[ihor-sviziev]

@andrewbess @engcom-Bravo, I think the issue is in the flow.

The admin user wants to log in to his/her account.

1. Customer put his credentials for login
2. He got asked for 2fa auth, and he puts the code
3. He gots redirected to a "change password page" (that actually has a lot of other fields). Admin changes his password, clicks "Save" button.

Expected result:

• ✅ You should see the message that your password was changed
• ✅ You should be redirected to the home admin page (because your main flow was a log in flow, not the change password)

Actual result:

• ✅ You should see the message that your password was changed
• ❌ You're still see the "change password" page, so you think that Magento asks you to change a password one more time.

[Franciscof-Serfe]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @Franciscof-Serfe. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @Franciscof-Serfe, here is your Magento Instance: https://bae5c16dabaa786afe2c15e3e1dd0a5c.instances-prod.magento-community.engineering Admin access: https://bae5c16dabaa786afe2c15e3e1dd0a5c.instances-prod.magento-community.engineering/admin_e540 Login: 3af993af Password: c6509c996081

[Franciscof-Serfe]

In addition to what @ihor-sviziev said, it would be great for the admin user experience if the message said something like:

"You saved the changes to the account" either "You saved changes to [field name]" (Password, email, name, etc.)

[engcom-Bravo]

@ihor-sviziev @Franciscof-Serfe Thanks for your Contribution!.

Hi @Gopaal3,

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

Steps to Reproduce

• Customer put his credentials for login
• He got asked for 2fa auth, and he puts the code
• He gots redirected to a "change password page" (that actually has a lot of other fields). Admin changes his password, clicks "Save" button.

Password has been changed but still we are in Change Password page.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-10886 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.

[AlexDev4]

@magento I am working on this

[m2-assistant[bot]]

Hi @AlexDev4! :wave: Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[AlexDev4]

@magento add to contributors team

[m2-assistant[bot]]

Hi @AlexDev4! :wave: Thank you for joining. Please accept team invitation :point_right: here :point_left: and add your comment one more time.

[AlexDev4]

@magento I am working on this

[Franciscof-Serfe]

@magento I'm working on this

[engcom-Bravo]

Hi,

Thank you for your contribution!

The Magento core engineering team is working on the issue which you have addressed in this PR. Team will cherry pick the commits from your PR and may do further implementation to cover few more scenarios as needed. We will reach out to you if we need more information. For now, you can pause work on this PR.

Thank you once again!