Custom policy - How to disable live input validation ?

Question

Custom policy - How to disable live input validation ?

Isaac Zolana 90

Using custom policies, we managed to customize our "forgot password" flow and design.

Unfortunately, there is an issue we are unable to fix. We are unable to disable the live validation of input fields.

When a user inserts value into the input field, from the moment he enters a single character, he is prompted with error messages.

live validation

Also, when we inspect the page, we can see an error message on the browser console related to the email pattern as the user types his email. User's image

We have a button at the bottom of the page that shows "SendVerificationCode". We would like for validation to start only when the user has clicked on that button once. Is that something we can configure on the custom policy ?

Other information : User's image

I am sure there is a way to fix this using javascript but I would like to know if there is a solution that can be applied to the custom policy. I know that version 2.1.6 selfasserted didn't have live validation, but we chose to use the latest version.

Other information :

setting.inputVerificationDelayTimeInMilliseconds metadata did not help me.

Isaac Zolana 90 Reputation points

2024-03-12T14:10:38.0366667+00:00
Using setting.inputVerificationDelayTimeInMilliseconds metadata has no effect on my project. It's either that or I don't understand that property well enough. I tried the live demo :

https://github.com/azure-ad-b2c/unit-tests/tree/main/technical-profiles/self-asserted#input-verification-delay-time-in-milliseconds

Even the demo confuses me. It mentions the following in the README.md : "To test the user experience, select on of the options (default, 100, or 6000), then select continue. In the next page, provide an incorrect password, such as 1111. Compare the time Azure AD B2C renders the error message."

Case 1 : set delay time to 100 milliseconds (0.1 seconds)

1- Select option 100

2- Press continue

3- Enter 1111 in one of the fields

4- Wait a few seconds

Expected result : An error message appears

Actual result : There is no error message. We have to press "continue" to see the error message (which is what I want).

Case 2 : set delay time to default milliseconds (2 seconds)

1- Select option "Default"

2- Press continue

3- Enter 1111 in one of the fields

4- Wait more than 2 seconds

Expected result : An error message appears

Actual result : There is no error message. We have to press "continue" to see the error message (which is what I want).

In short, I don't understand why I have live validation for my input fields. Setting setting.inputVerificationDelayTimeInMilliseconds metadata doesn't seem to delay the live validation. For example :

SQLCopy

<Item Key="setting.inputVerificationDelayTimeInMilliseconds">60000</Item>

The live demo doesn't help me much because It doesn't do what it mentions in the README yet somehow does what I want in to do in my project (which is to validate fields only when the button is pressed.)
Isaac Zolana 90 Reputation points

2024-03-12T15:56:23.4133333+00:00

@Marilee Turscak-MSFT Do you mind confirming if the live demo for setting.inputVerificationDelayTimeInMilliseconds metadata works as intended in a page layout of version 2.1.29, please ?
Evert van der Weit 0 Reputation points

2024-10-31T13:04:55.6233333+00:00
@Isaac Zolana Hi, I also ran into this issue and have a ongoing support ticket now to hopefully resolve this. I pinpointed the problem there, and will paste that response here for others as well:

I just did some more digging into this issue to see at which layout versions of the selfasserted page things stopped working. I found two things:

inputVerificationDelayTimeInMilliseconds setting

Up until 2.1.6 the setting.inputVerificationDelayTimeInMilliseconds works, and this is broken starting 2.1.7. The changelog shows this message, which probably is the culprit.

Fixed an accessibility bug to show inline error messages only on form submission.

Immediate verification bug

Up until 2.1.16 the verification is only shown when submitting the form (as per the 2.1.7 update). But starting at 2.1.17 the verification is always immediatly triggered. The changelog lists this message, which I suspect is the problem.

Enforce Validation Error Update on control change and enable continue on email verified

See changelog here

1 answer

Your answer

Isaac Zolana 90 Reputation points

2024-03-12T14:10:38.0366667+00:00

Using setting.inputVerificationDelayTimeInMilliseconds metadata has no effect on my project. It's either that or I don't understand that property well enough. I tried the live demo :

https://github.com/azure-ad-b2c/unit-tests/tree/main/technical-profiles/self-asserted#input-verification-delay-time-in-milliseconds

Even the demo confuses me. It mentions the following in the README.md : "To test the user experience, select on of the options (default, 100, or 6000), then select continue. In the next page, provide an incorrect password, such as 1111. Compare the time Azure AD B2C renders the error message."

Case 1 : set delay time to 100 milliseconds (0.1 seconds)

1- Select option 100

2- Press continue

3- Enter 1111 in one of the fields

4- Wait a few seconds

Expected result : An error message appears

Actual result : There is no error message. We have to press "continue" to see the error message (which is what I want).

Case 2 : set delay time to default milliseconds (2 seconds)

1- Select option "Default"

2- Press continue

3- Enter 1111 in one of the fields

4- Wait more than 2 seconds

Expected result : An error message appears

Actual result : There is no error message. We have to press "continue" to see the error message (which is what I want).

In short, I don't understand why I have live validation for my input fields. Setting setting.inputVerificationDelayTimeInMilliseconds metadata doesn't seem to delay the live validation. For example :

SQLCopy

<Item Key="setting.inputVerificationDelayTimeInMilliseconds">60000</Item>

The live demo doesn't help me much because It doesn't do what it mentions in the README yet somehow does what I want in to do in my project (which is to validate fields only when the button is pressed.)
Isaac Zolana 90 Reputation points

2024-03-12T15:56:23.4133333+00:00

@Marilee Turscak-MSFT Do you mind confirming if the live demo for setting.inputVerificationDelayTimeInMilliseconds metadata works as intended in a page layout of version 2.1.29, please ?
Evert van der Weit 0 Reputation points

2024-10-31T13:04:55.6233333+00:00

@Isaac Zolana Hi, I also ran into this issue and have a ongoing support ticket now to hopefully resolve this. I pinpointed the problem there, and will paste that response here for others as well:

I just did some more digging into this issue to see at which layout versions of the selfasserted page things stopped working. I found two things:

inputVerificationDelayTimeInMilliseconds setting

Up until 2.1.6 the setting.inputVerificationDelayTimeInMilliseconds works, and this is broken starting 2.1.7. The changelog shows this message, which probably is the culprit.

Fixed an accessibility bug to show inline error messages only on form submission.

Immediate verification bug

Up until 2.1.16 the verification is only shown when submitting the form (as per the 2.1.7 update). But starting at 2.1.17 the verification is always immediatly triggered. The changelog lists this message, which I suspect is the problem.

Enforce Validation Error Update on control change and enable continue on email verified

See changelog here

Answer 1

Marilee Turscak-MSFT 37,271 Microsoft Employee Moderator

Hi @Isaac Zolana ,

We have a metadata to control this behavior so that the validation does not appear until after the user has stopped typing.

Self-Asserted Technical Profile metadata:
setting.inputVerificationDelayTimeInMilliseconds	No	Improves user experience, by waiting for the user to stop typing, and then validate the value. Default value 2000 milliseconds. Check out the Live demo of this metadata.

This metadata is available for page layout version 1.2.0 and above. You can check this document for details:

https://learn.microsoft.com/en-us/azure/active-directory-b2c/self-asserted-technical-profile#metadata

Let me know if this helps and if you run into any issues.

If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar questions.

Isaac Zolana 90 Reputation points

2024-03-11T22:02:28.1833333+00:00
This solution has no effect on my project. It's either that or I don't understand that property well enough. I tried the live demo :

https://github.com/azure-ad-b2c/unit-tests/tree/main/technical-profiles/self-asserted#input-verification-delay-time-in-milliseconds

Even the demo confuses me. It mentions the following in the README.md : "To test the user experience, select on of the options (default, 100, or 6000), then select continue. In the next page, provide an incorrect password, such as 1111. Compare the time Azure AD B2C renders the error message."

Case 1 : set delay time to 100 milliseconds (0.1 seconds)

1- Select option 100

2- Press continue

3- Enter 1111 in one of the fields

4- Wait a few seconds

Expected result : An error message appears

Actual result : There is no error message. We have to press "continue" to see the error message (which is what I want).

Case 2 : set delay time to default milliseconds (2 seconds)

1- Select option "Default"

2- Press continue

3- Enter 1111 in one of the fields

4- Wait more than 2 seconds

Expected result : An error message appears

Actual result : There is no error message. We have to press "continue" to see the error message (which is what I want).

In short, I don't understand why I have live validation for my input fields. Setting setting.inputVerificationDelayTimeInMilliseconds metadata doesn't seem to delay the live validation. For example :

<Item Key="setting.inputVerificationDelayTimeInMilliseconds">60000</Item>

The live demo doesn't help me much because It doesn't do what it mentions in the README yet somehow does what I want in to do in my project (which is to validate fields only when the button is pressed.)

Share via

Custom policy - How to disable live input validation ?

1 answer

Your answer