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/msal-net-aad-b2c-considerations.md
+15-17Lines changed: 15 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
9
9
ms.subservice: develop
10
10
ms.topic: conceptual
11
11
ms.workload: identity
12
-
ms.date: 05/07/2020
12
+
ms.date: 02/21/2023
13
13
ms.author: henrymbugua
14
14
ms.reviewer: saeeda, jeferrie
15
15
ms.custom: "devx-track-csharp, aaddev"
@@ -29,9 +29,9 @@ This article applies to MSAL.NET 3.x. For MSAL.NET 2.x, see [Azure AD B2C specif
29
29
30
30
The authority format for Azure AD B2C is: `https://{azureADB2CHostname}/tfp/{tenant}/{policyName}`
31
31
32
-
-`azureADB2CHostname` - The name of the Azure AD B2C tenant plus the host. For example, *contosob2c.b2clogin.com*.
33
-
-`tenant` - The domain name or the directory (tenant) ID of the Azure AD B2C tenant. For example, *contosob2c.onmicrosoft.com* or a GUID, respectively.
34
-
-`policyName` - The name of the user flow or custom policy to apply. For example, a sign-up/sign-in policy like *b2c_1_susi*.
32
+
-`azureADB2CHostname` - The name of the Azure AD B2C tenant plus the host. For example, _contosob2c.b2clogin.com_.
33
+
-`tenant` - The domain name or the directory (tenant) ID of the Azure AD B2C tenant. For example, _contosob2c.onmicrosoft.com_ or a GUID, respectively.
34
+
-`policyName` - The name of the user flow or custom policy to apply. For example, a sign-up/sign-in policy like _b2c_1_susi_.
35
35
36
36
For more information about Azure AD B2C authorities, see [Set redirect URLs to b2clogin.com](../../active-directory-b2c/b2clogin.md).
For more information on the ROPC flow, see [Sign in with resource owner password credentials grant](v2-oauth-ropc.md).
118
118
119
-
The ROPC flow is **not recommended** because asking a user for their password in your application is not secure. For more information about this problem, see [What’s the solution to the growing problem of passwords?](https://news.microsoft.com/features/whats-solution-growing-problem-passwords-says-microsoft/).
119
+
The ROPC flow is **not recommended** because asking a user for their password in your application isn't secure. For more information about this problem, see [What’s the solution to the growing problem of passwords?](https://news.microsoft.com/features/whats-solution-growing-problem-passwords-says-microsoft/).
120
120
121
121
By using username/password in an ROPC flow, you sacrifice several things:
122
122
123
123
- Core tenets of modern identity: The password can be fished or replayed because the shared secret can be intercepted. By definition, ROPC is incompatible with passwordless flows.
124
-
- Users who need to do MFA won't be able to sign in (as there is no interaction).
124
+
- Users who use multi-factor authentication (MFA) won't be able to sign in as there's no interaction.
125
125
- Users won't be able to use single sign-on (SSO).
This`AcquireTokenByUsernamePassword` method takes the following parameters:
140
+
The`AcquireTokenByUsernamePassword` method takes the following parameters:
141
141
142
-
- The *scopes* for which to obtain an access token.
143
-
- A *username*.
144
-
- A SecureString *password* for the user.
142
+
- The _scopes_ for which to obtain an access token.
143
+
- A _username_.
144
+
- A SecureString _password_ for the user.
145
145
146
146
### Limitations of the ROPC flow
147
147
148
148
The ROPC flow **only works for local accounts**, where your users have registered with Azure AD B2C using an email address or username. This flow doesn't work when federating to an external identity provider supported by Azure AD B2C (Facebook, Google, etc.).
149
149
150
150
## Google auth and embedded webview
151
151
152
-
If you're using Google as an identity provider, we recommend you use the system browser as Google doesn't allow [authentication from embedded webviews](https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html). Currently, `login.microsoftonline.com` is a trusted authority with Google and will work with embedded webview. However, `b2clogin.com` is not a trusted authority with Google, so users will not be able to authenticate.
153
-
154
-
We'll provide an update to this [issue](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/688) if things change.
152
+
If you're using Google as an identity provider, we recommend you use the system browser as Google doesn't allow [authentication from embedded webviews](https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html). Currently, `login.microsoftonline.com` is a trusted authority with Google and will work with embedded webview. However, `b2clogin.com` isn't a trusted authority with Google, so users won't be able to authenticate.
155
153
156
154
## Token caching in MSAL.NET
157
155
@@ -186,6 +184,6 @@ For more information about specifying which claims are returned by your user flo
186
184
187
185
More details about acquiring tokens interactively with MSAL.NET for Azure AD B2C applications are provided in the following sample.
188
186
189
-
| Sample | Platform | Description|
190
-
|------ | -------- | -----------|
191
-
|[active-directory-b2c-xamarin-native](https://github.com/Azure-Samples/active-directory-b2c-xamarin-native)| Xamarin iOS, Xamarin Android, UWP | A Xamarin Forms app that uses MSAL.NET to authenticate users via Azure AD B2C and then access a web API with the tokens returned.|
|[active-directory-b2c-xamarin-native](https://github.com/Azure-Samples/active-directory-b2c-xamarin-native)| Xamarin iOS, Xamarin Android, UWP | A Xamarin Forms app that uses MSAL.NET to authenticate users via Azure AD B2C and then access a web API with the tokens returned.|
Copy file name to clipboardExpand all lines: articles/active-directory/governance/customize-workflow-schedule.md
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,31 +14,30 @@ ms.reviewer: krbain
14
14
ms.collection: M365-identity-device-management
15
15
---
16
16
17
-
# Customize the schedule of workflows (Preview)
17
+
# Customize the schedule of workflows
18
18
19
19
Workflows created using Lifecycle Workflows can be fully customized to match the schedule that fits your organization's needs. By default, workflows are scheduled to run every 3 hours, but the interval can be set as frequent as 1 hour, or as infrequent as 24 hours.
20
20
21
21
22
-
## Customize the schedule of workflows using Microsoft Graph
22
+
## Customize the schedule of workflows using the Azure portal
23
+
24
+
Workflows created within Lifecycle Workflows follow the same schedule that you define within the **Workflow Settings** page. To adjust the schedule, you'd follow these steps:
23
25
26
+
1. Sign in to the [Azure portal](https://portal.azure.com).
24
27
25
-
First, to view the current schedule interval of your workflows, run the following get call:
28
+
1. Select **Identity Governance** on the search bar near the top of the page.
26
29
27
-
```http
28
-
GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/settings
29
-
```
30
+
1. In the left menu, select **Lifecycle workflows (Preview)**.
30
31
32
+
1. Select **Workflow settings (Preview)** from the Lifecycle workflows overview page.
31
33
32
-
To customize a workflow in Microsoft Graph, use the following request and body:
1. On the workflow settings page you can set the schedule of workflows from an interval between 1-24.
35
+
:::image type="content" source="media/customize-workflow-schedule/workflow-schedule-settings.png" alt-text="Screenshot of the settings for workflow schedule.":::
36
+
1. After setting the workflow schedule, select save.
36
37
37
-
{
38
-
"workflowScheduleIntervalInHours":<Interval between 0-24>
39
-
}
38
+
## Customize the schedule of workflows using Microsoft Graph
40
39
41
-
```
40
+
To schedule workflow settings using API via Microsoft Graph, see: Update lifecycleManagementSettings [tenant settings for Lifecycle Workflows](/graph/api/resources/identitygovernance-lifecyclemanagementsettings).
Copy file name to clipboardExpand all lines: articles/aks/faq.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
@@ -233,7 +233,7 @@ Starting with version 1.2.0, Azure CNI sets Transparent mode as default for sing
233
233
234
234
### Bridge mode
235
235
236
-
As the name suggests, bridge mode Azure CNI, in a "just in time" fashion, will create a L2 bridge named "azure0". All the host side pod `veth` pair interfaces will be connected to this bridge. So Pod-Pod intra VM communication and the remaining traffic goes through this bridge. The bridge in question is a layer 2 virtual device that on its own cannot receive or transmit anything unless you bind one or more real devices to it. For this reason, eth0 of the Linux VM has to be converted into a subordinate to "azure0" bridge. This creates a complex network topology within the Linux VM and as a symptom CNI had to take care of other networking functions like DNS server update and so on.
236
+
As the name suggests, bridge mode Azure CNI, in a "just in time" fashion, will create an L2 bridge named "azure0". All the host side pod `veth` pair interfaces will be connected to this bridge. So Pod-Pod intra VM communication and the remaining traffic goes through this bridge. The bridge in question is a layer 2 virtual device that on its own cannot receive or transmit anything unless you bind one or more real devices to it. For this reason, eth0 of the Linux VM has to be converted into a subordinate to "azure0" bridge. This creates a complex network topology within the Linux VM and as a symptom CNI had to take care of other networking functions like DNS server update and so on.
| AKS Edge Essentials | Release version [1.0.406.0](https://github.com/Azure/AKS-Edge/releases/tag/1.0.406.0); Kubernetes version [1.24.3](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.3)|
21
22
22
23
The following providers and their corresponding Kubernetes distributions have successfully passed the conformance tests for Azure Arc-enabled Kubernetes:
0 commit comments