-
Notifications
You must be signed in to change notification settings - Fork 36
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
MFA support #37
Comments
Thanks @an-sush ... Hello @jmprieur should the authorization URL include the scope=openid to trigger the MFA or there is other way from AAD configurations? |
Hello @an-sush, I have tried the plug-in against my Azure AD tenant where MFA is enabled and it's working as expected. what exact error are you facing? |
@hkamel if the tenant admin requires MFA for each sign-in, the scope=openid would be enough. Now if the tenant admin requires MFA for other resources that need to be accessed by the plug-in (I don't think that this would be the case for SonarQube / SonarCloud), the scope for this resource should also be provided, in the case of an AAD V1 app (as there is no dynamic consent, contrary to AAD V2) |
A new draft release has been published 1.1-RC2 the announcement has been sent to the official SonarSource community to kick the official release. |
Hello,
I see that the plugin doesn't support Multi Factor Authentication. I have my Azure side setup with OpenID (to prompt for MFA after login) and I am not getting prompted for MFA since scope argument isn't passed:
&scope=openid
Refer:
https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-protocols-openid-connect-code
The text was updated successfully, but these errors were encountered: