Azure AD B2C users forced to log in every time opening MAUI android app

Andrew Gwilliam 0 Reputation points
2024-09-24T11:44:24.6166667+00:00

Hi

We currently have a Azure AD B2C custom policy for signing into MAUI android/IOS apps that makes a call to an Azure Function that checks whether the user logging in is a member of an Azure Group.

The Azure Function needs to be updated to .Net 8.0 and have the process mode changed. Have created a new function to replace the current one and it works fine.

The problem is the custom policy I have copied the current one and updated it to point to the new Azure Function and uploaded it under a new name.

The issue is that the original policy will let you sign in once and then you can refresh the token, so if you close the app on the device the user will only be asked to sign in once every 90 days.

The new custom policy forces the user to sign in every time. The only difference between the policies is that the below

Original Section

Updated Section

Both Azure Functions are available and working correctly.

With exception of the above section the only differences between the policies are the names.

Has anyone come across the before.

Thanks

Andrew Gwillliam

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,953 questions
.NET MAUI
.NET MAUI
A Microsoft open-source framework for building native device applications spanning mobile, tablet, and desktop.
3,453 questions
Microsoft Entra External ID
Microsoft Entra External ID
A modern identity solution for securing access to customer, citizen and partner-facing apps and services. It is the converged platform of Azure AD External Identities B2B and B2C. Replaces Azure Active Directory External Identities.
2,861 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pinaki Ghatak 4,210 Reputation points Microsoft Employee
    2024-09-25T09:59:44.6366667+00:00

    Hello @Andrew Gwilliam

    It seems like the issue is related to the difference in the two custom policies. The original policy allows users to refresh their token and only requires them to sign in once every 90 days, while the new policy requires users to sign in every time they open the app.

    Based on the information you provided, the only difference between the two policies is the section you mentioned. It's possible that this section is causing the issue.

    I would recommend reviewing the section in both policies to ensure that they are identical, and also checking if there are any other differences between the policies that could be causing the issue.

    I hope this helps.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.