| Getting Started | AAD Docs | Library Reference | Samples |
|---|
- About
- FAQ
- Changelog
- Prerequisites
- Version Support
- Installation
- Build and Test
- Usage
- Samples
- Security Reporting
- License
- Code of Conduct
The MSAL library for JavaScript enables client-side JavaScript applications to authenticate users using Azure AD work and school accounts (AAD), Microsoft personal accounts (MSA) and social identity providers like Facebook, Google, LinkedIn, Microsoft accounts, etc. through Azure AD B2C service. It also enables your app to get tokens to access Microsoft Cloud services such as Microsoft Graph.
The @azure/msal-react package described by the code in this folder uses the @azure/msal-browser package as a peer dependency to enable authentication in Javascript Single-Page Applications without backend servers. This version of the library uses the OAuth 2.0 Authorization Code Flow with PKCE. To read more about this protocol, as well as the differences between implicit flow and authorization code flow, see the section in the @azure/msal-browser readme.
-
@azure/msal-reactis meant to be used in Single-Page Application scenarios. -
Before using
@azure/msal-reactyou will need to register a Single Page Application in Azure AD to get a validclientIdfor configuration, and to register the routes that your app will accept redirect traffic on.
| MSAL React version | MSAL support status | Supported React versions |
|---|---|---|
| MSAL React v2 | Active development | 16, 17, 18 |
| MSAL React v1 | In maintenance | 16, 17, 18 |
Note: There have been no functional changes in the MSAL React v2 release.
The MSAL React package is available on NPM.
npm install react react-dom
npm install @azure/msal-react @azure/msal-browserSee the contributing.md file for more information.
To build the @azure/msal-react library, you can do the following:
// Install dev dependencies from root of repo
npm install
// Change to the msal-react package directory
cd lib/msal-react/
// To run build only for react package
npm run buildTo build both the @azure/msal-react library and @azure/msal-browser libraries, you can do the following:
// Install dev dependencies from root of repo
npm install
// Change to the msal-react package directory
cd lib/msal-react/
// To run build for react and browser packages
npm run build:all@azure/msal-react uses jest to run unit tests and coverage.
// To run tests
npm test
// To run tests with code coverage
npm run test:coverageFor help getting started with @azure/msal-react please see our getting started doc.
Migrating from react-aad-msal? Check out our migration guide.
Since @azure/msal-react is a wrapper around @azure/msal-browser many docs from the msal-browser repo are relevant here as well. For concepts specific to @azure/msal-react please see below
- Initialization
- Acquiring and using an access token
- Managing token lifetimes
- Managing Accounts
- Logging out
Our samples directory contains several example apps you can spin up to see how this library can be used in different contexts.
More advanced samples backed with a tutorial can be found in the Azure Samples space on GitHub:
- React SPA calling Express.js web API
- React SPA calling Express.js web API using App Roles and RBAC
- React SPA calling Microsoft Graph via Express.js web API using on-behalf-of flow
- Deployment tutorial for Azure Static Web Apps
If you find a security issue with our libraries or services please report it to [email protected] with as much detail as possible. Your submission may be eligible for a bounty through the Microsoft Bounty program. Please do not post security issues to GitHub Issues or any other public site. We will contact you shortly upon receiving the information. We encourage you to get notifications of when security incidents occur by visiting this page and subscribing to Security Advisory Alerts.
Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT License.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.