In .NET MAUI app, how can I avoid the iOS permission alert?

Get Help
,
1

Ready to post? :mag: First, try searching for your answer.
In .NET MAUI app, how can I avoid the iOS permission alert?

Alter
Alter554×708 26.6 KB

3 Likes
3

Hi @nkagarawal87,

Welcome to the Auth0 Community and sorry for the late reply.

To provide a bit of context, the main reason this prompt was added was to provide users more context about why a third-party website is about to appear, as well as surface the website domain to the user in a system-level prompt that can’t be faked by the app, more about this can be checked from this okta blog.

That alert box is displayed and managed by ASWebAuthenticationSession , because by default this API will store the session cookie in the shared Safari cookie jar. This makes single sign-on (SSO) possible. According to Apple, that requires user consent.

There is an out of the box solution only for the Auth0.swift SDK, detailed in this Knowledge Article .

For the MAUI integration, unfortunately there is no such existing solution at the moment in our current SDK. It is mentioned in this Knowledge Article that the ASWebAuthenticationSessionBrowser class is not yet exposed, so the workaround would be creating a custom Browser implementation.

i hope this helps your use case and provides general information as well.
Thanks,
Remus

4

Good day @remus.ivan, hope all is well!

A related question on the discussed dialog, we are implementing an automatic logout process after a period of inactivity on our C# MAUI Application. This process sends a Logout Request to the website with the Id Token Hint, which triggers the logout flow. On Android, the process works as expected, the web dialog opens, logs the user out, and then closes automatically.

However, on iOS, the automatic logout is interrupted by the above discussed confirmation dialog that prompts the user to continue to the logout page before proceeding. This additional step prevents the logout from happening seamlessly and blocks the automatic process.

Would you be able to suggest an alternative approach to handle this? Ideally, we would prefer to bypass the confirmation dialog entirely to maintain a smooth logout experience.

Best regards,