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
*Client_id* is the value that you previously noted as the application ID. *Offline_access* is optional if you want to receive a refresh token.
74
+
*Client_id* is the value that you previously noted as the application ID. *Offline_access* is optional if you want to receive a refresh token. The username and password that you use must be credentials from an existing user in your Azure AD B2C tenant.
75
75
76
76
The actual POST request looks like the following:
77
77
78
78
```
79
-
POST /yourtenant.onmicrosoft.com/B2C_1A_ROPC_Auth/oauth2/v2.0/token HTTP/1.1
79
+
POST /yourtenant.onmicrosoft.com/oauth2/v2.0/token?B2C_1_ROPC_Auth HTTP/1.1
80
80
Host: login.microsoftonline.com
81
81
Content-Type: application/x-www-form-urlencoded
82
82
@@ -100,7 +100,7 @@ A successful response with offline-access looks like the following example:
100
100
101
101
Construct a POST call like the one shown here with the information in the following table as the body of the request:
@@ -112,6 +112,24 @@ Construct a POST call like the one shown here with the information in the follow
112
112
113
113
*Client_id* and *resource* are the values that you previously noted as the application ID. *Refresh_token* is the token that you received in the authentication call mentioned previously.
114
114
115
+
A successful response looks like the following example:
## Implement with your preferred native SDK or use App-Auth
116
134
117
135
The Azure AD B2C implementation meets OAuth 2.0 standards for public client resource owner password credentials and should be compatible with most client SDKs. We have tested this flow extensively, in production, with AppAuth for iOS and AppAuth for Android. For the latest information, see [Native App SDK for OAuth 2.0 and OpenID Connect implementing modern best practices](https://appauth.io/).
Copy file name to clipboardExpand all lines: articles/active-directory/active-directory-applications-guiding-developers-for-lob-applications.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ ms.custom: seohack1
22
22
This guide provides an overview of developing line-of-business (LoB) applications for Azure Active Directory (AD).The intended audience is Active Directory/Office 365 global administrators.
23
23
24
24
## Overview
25
-
Building applications integrated with Azure AD gives users in your organization single sign-on with Office 365. Having the application in Azure AD gives you control over the authentication policy for the application. To learn more about conditional access and how to protect apps with multi-factor authentication (MFA) see [Configuring access rules](active-directory-conditional-access-azure-portal-get-started.md).
25
+
Building applications integrated with Azure AD gives users in your organization single sign-on with Office 365. Having the application in Azure AD gives you control over the authentication policy for the application. To learn more about conditional access and how to protect apps with multi-factor authentication (MFA) see [Configuring access rules](conditional-access/app-based-mfa.md).
26
26
27
27
Register your application to use Azure Active Directory. Registering the application means that your developers can use Azure AD to authenticate users and request access to user resources such as email, calendar, and documents.
28
28
@@ -54,7 +54,7 @@ Here’s what you, the global administrator, need to do to help developers make
54
54
* Suppress the default user consent experience
55
55
56
56
## Configure access rules
57
-
Configure per-application access rules to your SaaS apps. For example, you can require MFA or only allow access to users on trusted networks. The details for this are available in the document [Configuring access rules](active-directory-conditional-access-azure-portal-get-started.md).
57
+
Configure per-application access rules to your SaaS apps. For example, you can require MFA or only allow access to users on trusted networks. The details for this are available in the document [Configuring access rules](conditional-access/app-based-mfa.md).
58
58
59
59
## Configure the app to require user assignment and assign users
60
60
By default, users can access applications without being assigned. However, if the application exposes roles or if you want the application to appear on a user’s access panel, you should require user assignment.
@@ -75,6 +75,5 @@ For more information about user consent and the consent experience in Azure, see
75
75
76
76
## Related Articles
77
77
*[Enable secure remote access to on-premises applications with Azure AD Application Proxy](manage-apps/application-proxy.md)
78
-
*[Azure Conditional Access Preview for SaaS Apps](active-directory-conditional-access-azure-portal-get-started.md)
79
78
*[Managing access to apps with Azure AD](manage-apps/what-is-access-management.md)
80
79
*[Article Index for Application Management in Azure Active Directory](active-directory-apps-index.md)
Copy file name to clipboardExpand all lines: articles/active-directory/active-directory-apps-index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ Once you set up single sign-on to your apps and resources, you can then further
105
105
| Article Guide ||
106
106
|:---:| --- |
107
107
| An introduction to the conditional access capabilities offered across Azure AD, Office365, and Intune |[Managing Risk With Conditional Access](active-directory-conditional-access-azure-portal.md)|
108
-
| How to enable conditional access for the following types of resources |[Conditional Access for SaaS Apps](active-directory-conditional-access-azure-portal-get-started.md)<br /><br />[Conditional Access for Office 365 services](active-directory-conditional-access-device-policies.md)<br /><br />[Conditional Access for On-Premises Applications](active-directory-conditional-access-azure-portal.md)<br /><br />[Conditional Access for On-Premises Applications Published via Azure AD App Proxy](manage-apps/application-proxy-integrate-with-sharepoint-server.md)|
108
+
| How to enable conditional access for the following types of resources |[Conditional Access for SaaS Apps](conditional-access/app-based-conditional-access.md)<br /><br />[Conditional Access for Office 365 services](active-directory-conditional-access-device-policies.md)<br /><br />[Conditional Access for On-Premises Applications](active-directory-conditional-access-azure-portal.md)<br /><br />[Conditional Access for On-Premises Applications Published via Azure AD App Proxy](manage-apps/application-proxy-integrate-with-sharepoint-server.md)|
109
109
| How to register devices with Azure Active Directory in order to enable device-based conditional access policies |[Overview of Azure Active Directory Device Registration](active-directory-conditional-access-device-registration-overview.md)<br /><br />[How to Enable Automatic Device Registration for Domain Joined Windows Devices](active-directory-conditional-access-automatic-device-registration.md)<br />— [Steps for Windows 8.1 devices](active-directory-conditional-access-automatic-device-registration-setup.md)<br />— [Steps for Windows 7 devices](active-directory-conditional-access-automatic-device-registration-setup.md)|
110
110
111
111
| How to use the Microsoft Authenticator app for two-step verification |[Microsoft Authenticator](user-help/microsoft-authenticator-app-how-to.md)|
0 commit comments