@haui_lemmy@lemmy.giftedmc.com I’ve implemented the “log in with Microsoft”, “log in with Google”, etc buttons in ASP.NET Core + Identity before - most of them just use OAuth2, which works pretty much the same way no matter what provider you’re using.
OpenID Connect is an authorization layer built on top of OAuth2, so it could give you information about the user beyond just “they logged in and here’s an access token”. Maybe an OpenID Connect provider would be helpful in this use case - it seems to be designed to solve a problem much like this.
@haui_lemmy@lemmy.giftedmc.com I’ve implemented the “log in with Microsoft”, “log in with Google”, etc buttons in ASP.NET Core + Identity before - most of them just use OAuth2, which works pretty much the same way no matter what provider you’re using.
OpenID Connect is an authorization layer built on top of OAuth2, so it could give you information about the user beyond just “they logged in and here’s an access token”. Maybe an OpenID Connect provider would be helpful in this use case - it seems to be designed to solve a problem much like this.