Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

authenticateUserWithMicrosoft problem due to custom parameter prompt=consent #872

Open
tdnk opened this issue Mar 5, 2024 · 0 comments
Open

Comments

@tdnk
Copy link

tdnk commented Mar 5, 2024

Version 16.4.0

When using authenticateUserWithMicrosoft, prompt=consent is always added.

This blocks users from authenticate if the orginization doesn't allow non-admin users to consent wish to make admin consent for the Entreprise Application.

This approach is used more and more for higher security level in Azure AD.

When a admin has granted consent for all users (or group of users) for the App, adding prompt=consent causes the app to always prompt for user consent even when the admin already have made the consent.

Please see:

https://stackoverflow.com/questions/60111863/azure-active-directory-needs-admin-approval-after-setting-prompt-consent for a in dept description.

The best approach in the senario would be to allow prompt parameter to be controlled when calling authenticateUserWithMicrosoft

In FirebasePlugin.java the parameter is added in line 2296: customParameters.put("prompt", "consent");
In FirebasePlugin.m the parameter is added in line 1057: [customParameters setValue:@"consent" forKey:@"prompt"];

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant