You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/reference-v2-libraries.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Microsoft identity platform authentication libraries | Microsoft Docs
3
-
description: Compatible client libraries and server middleware libraries, and related library, source, and samples links, for the Microsoft identity platform endpoint.
3
+
description: Compatible client libraries and server middleware libraries, along with related library, source, and sample links, for the Microsoft identity platform endpoint.
# Microsoft identity platform authentication libraries
25
25
26
-
The [Microsoft identity platform endpoint](active-directory-v2-compare.md) supports the industry-standard OAuth 2.0 and OpenID Connect 1.0 protocols. The Microsoft Authentication Library (MSAL) is designed to work with the Microsoft identity platform endpoint. It's also possible to use open-source libraries that support OAuth 2.0 and OpenID Connect 1.0.
26
+
The [Microsoft identity platform endpoint](active-directory-v2-compare.md) supports the industry-standard OAuth 2.0 and OpenID Connect 1.0 protocols. The Microsoft Authentication Library (MSAL) is designed to work with the Microsoft identity platform endpoint. You can also use open-source libraries that support OAuth 2.0 and OpenID Connect 1.0.
27
27
28
-
It's recommended that you use libraries written by protocol domain experts who follow a Security Development Lifecycle (SDL) methodology, like [the one followed by Microsoft][Microsoft-SDL]. If you decide to hand-code for the protocols, you should follow a methodology like Microsoft's SDL and pay close attention to the security considerations in the standards specifications for each protocol.
28
+
We recommend that you use libraries written by protocol domain experts who follow a Security Development Lifecycle (SDL) methodology. Such libraries include [the one that Microsoft follows][Microsoft-SDL]. If you handcode for the protocols, you should follow a methodology such as Microsoft SDL. Pay close attention to the security considerations in the standards specifications for each protocol.
29
29
30
30
> [!NOTE]
31
-
> Looking for the Azure AD authentication library (ADAL)? Checkout the [ADAL library guide](active-directory-authentication-libraries.md).
31
+
> Are you looking for the Azure Active Directory Authentication Library (ADAL)? Check out the [ADAL library guide](active-directory-authentication-libraries.md).
32
32
33
33
## Types of libraries
34
34
35
-
Microsoft identity platform endpoint works with two types of libraries:
35
+
The Microsoft identity platform endpoint works with two types of libraries:
36
36
37
-
***Client libraries**: Native clients and servers use client libraries to get access tokens for calling a resource, such as Microsoft Graph.
38
-
***Server middleware libraries**: Web apps use server middleware libraries for user sign-in. Web APIs use server middleware libraries to validate tokens that are sent by native clients or by other servers.
37
+
***Client libraries**: Native clients and servers use client libraries to acquire access tokens for calling a resource such as Microsoft Graph.
38
+
***Server middleware libraries**: Web apps use server middleware libraries for user signin. Web APIs use server middleware libraries to validate tokens that are sent by native clients or by other servers.
39
39
40
40
## Library support
41
41
42
42
Libraries come in two support categories:
43
43
44
44
***Microsoft-supported**: Microsoft provides fixes for these libraries and has done SDL due diligence on these libraries.
45
-
***Compatible**: Microsoft has tested these libraries in basic scenarios and confirmed that they work with the Microsoft identity platform endpoint. Microsoft does not provide fixes for these libraries and has not done a review of these libraries. Issues and feature requests should be directed to the library’s open-source project.
45
+
***Compatible**: Microsoft has tested these libraries in basic scenarios and has confirmed that they work with the Microsoft identity platform endpoint. Microsoft doesn't provide fixes for these libraries and hasn't done a review of these libraries. Issues and feature requests should be directed to the library’s open-source project.
46
46
47
-
For a list of libraries that work with the Microsoft identity platform endpoint, see the next sections in this article.
47
+
For a list of libraries that work with the Microsoft identity platform endpoint, see the following sections.
48
48
49
49
## Microsoft-supported client libraries
50
50
51
-
Client authentication libraries are used to acquire a token to call a protected Web API
51
+
Use client authentication libraries to acquire a token for calling a protected web API.
## Microsoft-supported server middleware libraries
65
65
66
-
Middleware libraries are used to protect Web applications and Web APIs. For web app or Web API written with ASP.NET or ASP.NET Core, the middleware libraries are used by ASP.NET / ASP.NET Core
66
+
Use middleware libraries to help protect web applications and web APIs. Web apps or web APIs written with ASP.NET or ASP.NET Core use the middleware libraries.
||[The PHP League oauth2-client](https://github.com/thephpleague/oauth2-client)|[Version 1.4.2](https://github.com/thephpleague/oauth2-client/releases/tag/1.4.2)|[oauth2-client](https://github.com/thephpleague/oauth2-client/)||
For any standards-compliant library you can use the Microsoft identity platform endpoint, thus it’s important to know where to go for support.
87
+
For any standards-compliant library, you can use the Microsoft identity platform endpoint. It’s important to know where to go for support:
88
88
89
89
* For issues and new feature requests in library code, contact the library owner.
90
90
* For issues and new feature requests in the service-side protocol implementation, contact Microsoft.
91
-
*[File a feature request](https://feedback.azure.com/forums/169401-azure-active-directory) for additional features you would like to see in the protocol.
92
-
*[Create a support request](https://docs.microsoft.com/azure/azure-supportability/how-to-create-azure-support-request) if you find an issue where the Microsoft identity platform endpoint is not compliant with OAuth 2.0 or OpenID Connect 1.0.
91
+
*[File a feature request](https://feedback.azure.com/forums/169401-azure-active-directory) for additional features you want to see in the protocol.
92
+
*[Create a support request](https://docs.microsoft.com/azure/azure-supportability/how-to-create-azure-support-request) if you find an issue where the Microsoft identity platform endpoint isn't compliant with OAuth 2.0 or OpenID Connect 1.0.
0 commit comments