In MSAL server-side applications include web apps, web APIs, and long-running daemon services.
These scenarios are generally considered secure enough for MSAL to store credentials, allowing a single MSAL instance to make token requests on behalf of multiple users using the same basic credentials.
A group of web authentication samples using OpenId Connect and the Microsoft Identity platform
- Use MSAL Java in a web application to sign in users with Microsoft Entra ID
- Source code can be found in the msal-java-webapp-sample directory, as well as the README for configuring and running the sample
- Use MSAL Java in a web application to sign in users Azure Active Directory B2C
- Source code can be found in the msal-b2c-web-sample directory, as well as the README for configuring and running the sample
- Use MSAL Java alongside Spring Security to sign in users with Microsoft Entra ID
- Source code can be found in the msal-spring-security-web-app directory, as well as the README for configuring and running the sample
- Use MSAL Java in a web application to sign in users with Microsoft Entra ID, and obtain an access token for a separate web API
- Source code can be found in the msal-web-api-sample directory, as well as the README for configuring and running the sample
How to use the Microsoft Identity platform to access user data in a long-running, non-interactive process:
- An application which uses the client credentials flow with a certificate to obtain an access token for Microsoft Graph
- Source code can be found in the msal-client-credential-certificate directory, as well as the README for configuring and running the sample
- An application which uses the client credentials flow with a secret to obtain an access token for Microsoft Graph
- Source code can be found in the msal-client-credential-secret directory, as well as the README for configuring and running the sample