This would be hugely helpful

Hey,

Sure can do!

> Could you please be more specific? What is desired usage scenario?
In the case of small to larger corporations, the focus goes always further into the direction of SSO, thus it would be beneficial for Plesk to also account for further growth in this security-related sector. This methodology of only having 1 Login to allow users to actually remember a password and have sufficient two factor or even more, is a good advantage in future proving.

> What are expected benefits of this feature in comparison with other already implemented social login methods?
I would argue, that allowing multiple authentication methods would allow a higher access rate of users. Also instead of having 1 extension for Google etc. and then another for just LDAP, why can't you create one extension allowing for example:
LDAP, OAuthv2(likely what you are using for google etc.)

And then let the customer make the implementation for each, this way I could for example use Azure AD using OAuth, even tho you technically didn't account for it, but wrote code to support your Google, Facebook etc. login. I think the SSL It! was a great success and could be an example of bringing extensions together into one product to provide even better solutions. ( easier to implement and control for example )

I would say, support for OIDC should be sufficient.

More IdPs are supporting OIDC, including Azure AD

Hi,

Our company is using Azure AD for account management. Currently, Plesk Social Login is supporting Google, GitHub and Facebook.

Could Microsoft SSO be supported as well?

This would enable us to give named user access to Plesk while managing account status at a central point (i.e.: disable at one place only).

Please see attached.

Thanks!