Why azure B2C custom login journey using custom policy shows deleted alternate phone number?

Question

Hello,

We have a custom policy created for login journey which shows customized interface with dropdown to select either of phone number or alternate phone number to select as a part of MFA step. If only primary phone number is available then it should not show a dropdown list.

When we are deleting the alternate phone number it still shows the old number in claims and dropdown list appears with both numbers. Once we clear the browser cache it works as expected and does not show dropdown list as expected.

What are the ways to not to show deleted number in MFA without clearing browser cache.

Thanks,

Snehal Thube

Answer 1

Hi @Snehal Thube , one way to avoid this issue is to configure your custom policy to refresh the claims when the user logs in. This can be done by adding a technical profile to your custom policy that retrieves the latest user information from the directory and updates the claims accordingly.

Please let me know if you have any questions and I can help you further.

If this answer helps you please mark "Accept Answer" so other users can reference it.

Thank you,

James