Once the "Confirm Password" input matches the "New Password" input, if the "New Password" changes there will be no error message indicating that the "Confirm Password" is invalid Note : The UI issues can be ignored. Other information : I am using predicates for validation I am using selfasserted page layout version 2.1.29

Looks like a bug. Ensure the browser cache is cleared and/or hard reload your policies. If the issue persists you will have to reach community engineers so that they can report the bug to the product team. Adding @Shweta Mathur and @Marilee Turscak-MSFT to the loop. Let me know if you need additional or more detailed guidance. If the answer was helpful, please accept it and rate it so that others facing a similar issue can easily find a solution.

Custom policy : Reenter password validation bug

Accepted answer

Alfredo Revilla - Senior Freelance SWE, SWA, IAM 27,016 Reputation points

2024-03-26T23:50:08.51+00:00

Looks like a bug. Ensure the browser cache is cleared and/or hard reload your policies. If the issue persists you will have to reach community engineers so that they can report the bug to the product team.

Adding @Shweta Mathur and @Marilee Turscak-MSFT to the loop.

Let me know if you need additional or more detailed guidance. If the answer was helpful, please accept it and rate it so that others facing a similar issue can easily find a solution.
Please sign in to rate this answer.
Isaac Zolana 80 Reputation points

2024-03-27T14:43:41.84+00:00

Hi, thanks for the quick answer. I can confirm that I cleared the cache and even tested it on incognito mode.

To fix the issue I had to use a workaround which I am not entirely satisfied of. In short, I used "dispatchEvent" in JavaScript to trigger the error in the "Confirm Password" field like so :

const newPasswordInput = document.getElementById("newPassword"); const confirmPasswordInput = document.getElementById("reenterPassword"); newPasswordInput.addEventListener('keydown', () => { confirmPasswordInput.dispatchEvent(new Event('keydown', { bubbles: true })); }); newPasswordInput.addEventListener('input', () => { confirmPasswordInput.dispatchEvent(new Event('keydown', { bubbles: true })); }); confirmPasswordInput.addEventListener('paste', () => { confirmPasswordInput.dispatchEvent(new Event('keydown', { bubbles: true })); }); confirmPasswordInput.addEventListener('input', () => { confirmPasswordInput.dispatchEvent(new Event('keydown', { bubbles: true })); });

Extra context :

Our custom policy will mainly be used for mobile applications, and we wanted to handle pasting as well as autofill (a feature that mobile applications have to autofill inputs). This is why you see all these events being listened to so we can trigger a "keydown" event on the "Confirm Password" input.

Alfredo Revilla - Senior Freelance SWE, SWA, IAM 27,016 Reputation points

2024-03-27T19:02:10.89+00:00

The workaround looks fine. To reach the community engineers so that the bug is properly addressed, send an email to azcommunity@microsoft.com with Attn: S+I including this post URL and optionally your custom policies source code and/or test URL.

Let me know if you need additional or more detailed guidance. If the answer was helpful, please accept it and rate it so that others facing a similar issue can easily find a solution.
Sign in to comment

Custom policy : Reenter password validation bug

0 additional answers