Cannot edit customer using inline edit if password is expired

[JeroenVanLeusden]

Preconditions

1. Magento v2.2.5

Steps to reproduce

1. Set admin/security/password_is_forced to 0 (Recommended).
2. Make sure Password Lifetime is past so the message It's time to change your password. is shown.
3. Open customer grid and try to edit and save using inline editor.

Expected result

1. Customer is saved.

Actual result

1. Above grid the message It's time to change your password. is shown

[magento-engcom-team]

Hi @JeroenVanLeusden. 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 (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label G1 Passed will be added to the issue automatically. Please, edit issue description if needed, until label G1 Passed appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add G2 Passed label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label acknowledged once verification is complete.

• 7. Make sure that automatic system confirms that report is acknowledged.

[magento-engcom-team]

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-95128, MAGETWO-95129 were created

[dmytro-ch]

Looks like the issue cannot be reproduced on Magento 2.2.6 and 2.3 versions.

[ghost]

@dmytro-ch Please try again -> Open customer grid and try to edit and save using inline editor.
I'm able to reproduce on both instances.

[ghost]

@dmytro-ch on 2.2-dev

on 2.3-dev

[dmytro-ch]

@engcom-backlog-nazar, thank you for the details!
It was my mistake, now I can reproduce the error.
I will handle this issue.

[slavvka]

Hi @JeroenVanLeusden. Thank you for your report.
The issue has been fixed in #18308 by @dmytro-ch in 2.3-develop branch
Related commit(s):

• 2eeb65ccd6201d95a667e5ccaf348b30d46317fe
• 34830c61154ae4b199eef531901164a417ef6c7d

The fix will be available with the upcoming 2.3.1 release.

[magento-engcom-team]

Hi @JeroenVanLeusden. Thank you for your report.
The issue has been fixed in #18414 by @dmytro-ch in 2.2-develop branch
Related commit(s):

• 33ba243a068b9e695fdb2520ab463aa3d5911f1a
• 2668f2df768d749f2069195715188afbf6d99348

The fix will be available with the upcoming 2.2.8 release.