MicrosoftMicrosoftInstructions unclear, ****** stuck in blender.
I'm not aware what your marking calls things today but we are authenticating O365 users for our services. We initiate the authentication by redirecting users to
https://login.windows.net/common/oauth2/authorize?response_type=code&resource=https://graph.windows.net&client_id=$CLIENT_ID&redirect_uri=$REDIRECT_URL
and then later request data from https://login.windows.net/common/oauth2/token and we are only interested in the "oid" data. If available, we also show "given_name" and "family_name" back to the user but we don't actually need those. We don't use any libraries except standard HTTP over TLS implementation.
Do we need to use ADAL or MSAL in the future or is this API going to work in future, too?
The Azure portal UI does have warnings such as
Starting November 9th, 2020 end users will no longer be able to grant consent to newly registered multitenant apps without verified publishers.Publisher domain: Unverified
The application’s consent screen will show ‘Unverified’.Due to temporary differences in supported functionality, we don't recommend enabling personal Microsoft accounts for an existing registration. If you need to enable personal accounts, you can do so using the manifest editor.This application is using Azure AD Graph API, which is on a deprecation path. Starting June 30th, 2020 we will no longer add any new features to Azure AD Graph API. We strongly recommend that you upgrade your application to use Microsoft Graph API instead of Azure AD Graph API to access Azure Active Directory resources.and everything still works just fine. Should I just ignore all those warnings, whatever they try to say?