-
Notifications
You must be signed in to change notification settings - Fork 13
Home
For the basics, see OAuth 2 overview.
The table shows how different services are able to play the Authorization Server role in the different OAuth 2 grants.
| ADFS 3.0 | Azure AD | Azure ACS | Thinktecture AuthorizationServer
---------------------------------|----------|----------|-----------|--------------------------------- Authorization Code Grant | yes | yes | partly | yes Implicit Grant | no | no | no | yes Resource Owner Credentials Grant | no | yes | no | yes Client Credentials Grant | no | yes | yes | yes
For the details, see:
For developers, there is also the Microsoft.Owin.Security.OAuth components, which has a base implementation of all the OAuth 2 grants. See the details here: OAuth 2 in Microsoft.Owin.Security.OAuth.
This is a deprecated protocol, and is only supported by ACS. Some other Azure services use this protocol though, for example Azure Service Bus.
For more information, see The OAuth Wrap Protocol.
| ADFS 3.0 | Azure AD | Azure ACS
---------------------------------|----------|----------|---------- Client Account and Password Profile | no | no | yes Assertion Profile | no | no | ? Username and Password Profile | no | no | no Web App Profile | no | no | ? Rich App Profile | no | no | ?
For the details, see: