Skip to content

Commit 76a5e95

Browse files
authored
Merge branch 'master' into dataflow-1
2 parents 6ef62c2 + 410d350 commit 76a5e95

File tree

1,894 files changed

+31608
-19451
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,894 files changed

+31608
-19451
lines changed

.openpublishing.redirection.json

Lines changed: 308 additions & 53 deletions
Large diffs are not rendered by default.

articles/active-directory-b2c/active-directory-b2c-faqs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ There are two common reasons for why the Azure AD extension is not working for y
2323

2424
### Can I use Azure AD B2C features in my existing, employee-based Azure AD tenant?
2525

26-
Azure AD and Azure AD B2C are separate product offerings and cannot coexist in the same tenant. An Azure AD tenant represents an organization. An Azure AD B2C tenant represents a collection of identities to be used with relying party applications. With custom policies (in public preview), Azure AD B2C can federate to Azure AD allowing authentication of employees in an organization.
26+
Azure AD and Azure AD B2C are separate product offerings and cannot coexist in the same tenant. An Azure AD tenant represents an organization. An Azure AD B2C tenant represents a collection of identities to be used with relying party applications. With custom policies, Azure AD B2C can federate to Azure AD allowing authentication of employees in an organization.
2727

2828
### Can I use Azure AD B2C to provide social login (Facebook and Google+) into Office 365?
2929

@@ -118,7 +118,7 @@ No, Azure AD B2C does not support the same set of reports as Azure AD Premium. H
118118

119119
### Can I localize the UI of pages served by Azure AD B2C? What languages are supported?
120120

121-
Yes! Read about [language customization](active-directory-b2c-reference-language-customization.md), which is in public preview. We provide translations for 36 languages, and you can override any string to suit your needs.
121+
Yes, see [language customization](active-directory-b2c-reference-language-customization.md). We provide translations for 36 languages, and you can override any string to suit your needs.
122122

123123
### Can I use my own URLs on my sign-up and sign-in pages that are served by Azure AD B2C? For instance, can I change the URL from contoso.b2clogin.com to login.contoso.com?
124124

articles/active-directory-b2c/active-directory-b2c-quickstarts-spa.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,12 @@ Azure Active Directory B2C (Azure AD B2C) provides cloud identity management to
2121

2222
## Prerequisites
2323

24-
- [Visual Studio 2019](https://www.visualstudio.com/downloads/) with the **ASP.NET and web development** workload.
25-
- Install [Node.js](https://nodejs.org/en/download/)
26-
- A social account from either Facebook, Google, or Microsoft.
27-
- [Download a zip file](https://github.com/Azure-Samples/active-directory-b2c-javascript-msal-singlepageapp/archive/master.zip) or clone the sample web app from GitHub.
24+
- [Visual Studio 2019](https://www.visualstudio.com/downloads/) with the **ASP.NET and web development** workload
25+
- [Node.js](https://nodejs.org/en/download/)
26+
- Social account from Facebook, Google, or Microsoft
27+
- Code sample from GitHub: [active-directory-b2c-javascript-msal-singlepageapp](https://github.com/Azure-Samples/active-directory-b2c-javascript-msal-singlepageapp)
28+
29+
You can [download the zip archive](https://github.com/Azure-Samples/active-directory-b2c-javascript-msal-singlepageapp/archive/master.zip) or clone the repository:
2830

2931
```
3032
git clone https://github.com/Azure-Samples/active-directory-b2c-javascript-msal-singlepageapp.git

articles/active-directory-b2c/active-directory-b2c-reference-manage-sso-and-token-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,5 +98,5 @@ To change your session behavior and SSO configurations, you add a **UserJourneyB
9898
The following values are configured in the previous example:
9999

100100
- **Single sign on (SSO)** - Single sign-on is configured with the **SingleSignOn**. The applicable values are `Tenant`, `Application`, `Policy`, and `Suppressed`.
101-
- **Web app session lifetime (minutes)** - The web app session lifetime is set with the **SessionExpiryInSeconds** element. The default value is 86400 seconds (1440 minutes).
102101
- **Web app session time-out** - The web app session timeout is set with the **SessionExpiryType** element. The applicable values are `Absolute` and `Rolling`.
102+
- **Web app session lifetime** - The web app session lifetime is set with the **SessionExpiryInSeconds** element. The default value is 86400 seconds (1440 minutes).

articles/active-directory-b2c/active-directory-b2c-reference-oauth-code.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ POST {tenant}.onmicrosoft.com/{policy}/oauth2/v2.0/token HTTP/1.1
168168
Host: {tenant}.b2clogin.com
169169
Content-Type: application/x-www-form-urlencoded
170170
171-
grant_type=refresh_token&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6&client_secret=JqQX2PNo9bpM0uEihUPzyrh&scope=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6 offline_access&refresh_token=AwABAAAAvPM1KaPlrEqdFSBzjqfTGBCmLdgfSTLEMPGYuNHSUYBrq...&redirect_uri=urn:ietf:wg:oauth:2.0:oob
171+
grant_type=refresh_token&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6&scope=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6 offline_access&refresh_token=AwABAAAAvPM1KaPlrEqdFSBzjqfTGBCmLdgfSTLEMPGYuNHSUYBrq...&redirect_uri=urn:ietf:wg:oauth:2.0:oob
172172
```
173173

174174
| Parameter | Required? | Description |
@@ -222,4 +222,4 @@ To try these requests yourself, complete the following steps. Replace the exampl
222222

223223
1. [Create an Azure AD B2C directory](active-directory-b2c-get-started.md). Use the name of your directory in the requests.
224224
2. [Create an application](active-directory-b2c-app-registration.md) to obtain an application ID and a redirect URI. Include a native client in your app.
225-
3. [Create your user flows](active-directory-b2c-reference-policies.md) to obtain your user flow names.
225+
3. [Create your user flows](active-directory-b2c-reference-policies.md) to obtain your user flow names.

articles/active-directory-b2c/active-directory-b2c-reference-oidc.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ POST {tenant}.onmicrosoft.com/{policy}/oauth2/v2.0/token HTTP/1.1
137137
Host: {tenant}.b2clogin.com
138138
Content-Type: application/x-www-form-urlencoded
139139
140-
grant_type=authorization_code&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6&scope=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6 offline_access&code=AwABAAAAvPM1KaPlrEqdFSBzjqfTGBCmLdgfSTLEMPGYuNHSUYBrq...&redirect_uri=urn:ietf:wg:oauth:2.0:oob&client_secret=<your-application-secret>
140+
grant_type=authorization_code&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6&scope=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6 offline_access&code=AwABAAAAvPM1KaPlrEqdFSBzjqfTGBCmLdgfSTLEMPGYuNHSUYBrq...&redirect_uri=urn:ietf:wg:oauth:2.0:oob
141141
```
142142

143143
| Parameter | Required | Description |
@@ -206,7 +206,7 @@ POST {tenant}.onmicrosoft.com/{policy}/oauth2/v2.0/token HTTP/1.1
206206
Host: {tenant}.b2clogin.com
207207
Content-Type: application/x-www-form-urlencoded
208208
209-
grant_type=refresh_token&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6&scope=openid offline_access&refresh_token=AwABAAAAvPM1KaPlrEqdFSBzjqfTGBCmLdgfSTLEMPGYuNHSUYBrq...&redirect_uri=urn:ietf:wg:oauth:2.0:oob&client_secret=<your-application-secret>
209+
grant_type=refresh_token&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6&scope=openid offline_access&refresh_token=AwABAAAAvPM1KaPlrEqdFSBzjqfTGBCmLdgfSTLEMPGYuNHSUYBrq...&redirect_uri=urn:ietf:wg:oauth:2.0:oob
210210
```
211211

212212
| Parameter | Required | Description |

articles/active-directory-b2c/active-directory-b2c-setup-commonaad-custom.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ You can define Azure AD as a claims provider by adding Azure AD to the **ClaimsP
7979
<Description>Login with your Contoso account</Description>
8080
<Protocol Name="OpenIdConnect"/>
8181
<Metadata>
82-
<Item Key="METADATA">https://login.windows.net/common/.well-known/openid-configuration</Item>
82+
<Item Key="METADATA">https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration</Item>
8383
<!-- Update the Client ID below to the Application ID -->
8484
<Item Key="client_id">00000000-0000-0000-0000-000000000000</Item>
8585
<Item Key="response_types">code</Item>
@@ -89,9 +89,9 @@ You can define Azure AD as a claims provider by adding Azure AD to the **ClaimsP
8989
<Item Key="UsePolicyInRedirectUri">false</Item>
9090
<Item Key="DiscoverMetadataByTokenIssuer">true</Item>
9191
<!-- The key below allows you to specify each of the Azure AD tenants that can be used to sign in. Update the GUIDs below for each tenant. -->
92-
<Item Key="ValidTokenIssuerPrefixes">https://sts.windows.net/00000000-0000-0000-0000-000000000000,https://sts.windows.net/11111111-1111-1111-1111-111111111111</Item>
92+
<Item Key="ValidTokenIssuerPrefixes">https://login.microsoftonline.com/00000000-0000-0000-0000-000000000000,https://login.microsoftonline.com/11111111-1111-1111-1111-111111111111</Item>
9393
<!-- The commented key below specifies that users from any tenant can sign-in. Uncomment if you would like anyone with an Azure AD account to be able to sign in. -->
94-
<!-- <Item Key="ValidTokenIssuerPrefixes">https://sts.windows.net/</Item> -->
94+
<!-- <Item Key="ValidTokenIssuerPrefixes">https://login.microsoftonline.com/</Item> -->
9595
</Metadata>
9696
<CryptographicKeys>
9797
<Key Id="client_secret" StorageReferenceId="B2C_1A_AADAppSecret"/>
@@ -125,17 +125,17 @@ You can define Azure AD as a claims provider by adding Azure AD to the **ClaimsP
125125
### Restrict access
126126
127127
> [!NOTE]
128-
> Using `https://sts.windows.net` as the value for **ValidTokenIssuerPrefixes** allows all Azure AD users to sign in to your application.
128+
> Using `https://login.microsoftonline.com/` as the value for **ValidTokenIssuerPrefixes** allows all Azure AD users to sign in to your application.
129129
130130
You need to update the list of valid token issuers and restrict access to a specific list of Azure AD tenant users who can sign in.
131131
132-
To obtain the values, look at the OpenID Connect discovery metadata for each of the Azure AD tenants that you would like to have users sign in from. The format of the metadata URL is similar to `https://login.windows.net/your-tenant/.well-known/openid-configuration`, where `your-tenant` is your Azure AD tenant name. For example:
132+
To obtain the values, look at the OpenID Connect discovery metadata for each of the Azure AD tenants that you would like to have users sign in from. The format of the metadata URL is similar to `https://login.microsoftonline.com/your-tenant/v2.0/.well-known/openid-configuration`, where `your-tenant` is your Azure AD tenant name. For example:
133133
134-
`https://login.windows.net/fabrikam.onmicrosoft.com/.well-known/openid-configuration`
134+
`https://login.microsoftonline.com/fabrikam.onmicrosoft.com/v2.0/.well-known/openid-configuration`
135135
136136
Perform these steps for each Azure AD tenant that should be used to sign in:
137137
138-
1. Open your browser and go to the OpenID Connect metadata URL for the tenant. Find the **issuer** object and record its value. It should look similar to `https://sts.windows.net/00000000-0000-0000-0000-000000000000/`.
138+
1. Open your browser and go to the OpenID Connect metadata URL for the tenant. Find the **issuer** object and record its value. It should look similar to `https://login.microsoftonline.com/00000000-0000-0000-0000-000000000000/`.
139139
1. Copy and paste the value into the **ValidTokenIssuerPrefixes** key. Separate multiple issuers with a comma. An example with two issuers appears in the previous `ClaimsProvider` XML sample.
140140
141141
### Upload the extension file for verification

articles/active-directory-b2c/active-directory-b2c-tutorials-spa-webapi.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ git clone https://github.com/Azure-Samples/active-directory-b2c-dotnetcore-webap
6666

6767
### Configure the web API
6868

69-
1. Open the *B2C-WebApi/**appsettings.json*** file in Visual Studio or Visual Studio Code.
69+
1. Open the <em>B2C-WebApi/**appsettings.json**</em> file in Visual Studio or Visual Studio Code.
7070
1. Modify the `AzureAdB2C` block to reflect your tenant name, the application ID of the web API application, the name of your sign-up/sign-in policy, and the scopes you defined earlier. The block should look similar to the following example (with appropriate `Tenant` and `ClientId` values):
7171

7272
```json

articles/active-directory-b2c/active-directory-b2c-ui-customization-custom.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ Validate that you're ready by performing the following steps:
114114

115115
To configure UI customization, you copy the **ContentDefinition** and its child elements from the base file to the extensions file.
116116

117-
1. Open the base file of your policy. For example, *`SocialAndLocalAccounts/`**`TrustFrameworkBase.xml`***. This is one of the policy files included in the custom policy starter pack, which you should have obtained in the prerequisite, [Get started with custom policies](https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-get-started-custom).
117+
1. Open the base file of your policy. For example, <em>`SocialAndLocalAccounts/`**`TrustFrameworkBase.xml`**</em>. This is one of the policy files included in the custom policy starter pack, which you should have obtained in the prerequisite, [Get started with custom policies](https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-get-started-custom).
118118
1. Search for and copy the entire contents of the **ContentDefinitions** element.
119119
1. Open the extension file. For example, *TrustFrameworkExtensions.xml*. Search for the **BuildingBlocks** element. If the element doesn't exist, add it.
120120
1. Paste the entire contents of the **ContentDefinitions** element that you copied as a child of the **BuildingBlocks** element.

articles/active-directory-b2c/page-layout.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,17 @@ To set up a page layout, use the following table to find **DataUri** values.
6464

6565
Page layout packages are periodically updated to include fixes and improvements in their page elements. The following change log specifies the changes introduced in each version.
6666

67+
### 1.2.0
68+
- All pages
69+
- Accessibility fixes
70+
- You can now add the `data-preload="true"` attribute in your HTML tags to control the load order for CSS and JavaScript. Scenarios include:
71+
- Use this on your CSS link to load the CSS at the same time as your HTML so that it doesn't 'flicker' between loading the files
72+
- This attribute allows you to control the order in which your Script tags are fetched and executed before the page load
73+
- Email field is now `type=email` and mobile keyboards will provide the correct suggestions
74+
- Support for Chrome translate
75+
- Unified and self-asserted page
76+
- The username/email and password fields now use the form HTML element. This will now allow Edge and IE to properly save this information
77+
6778
### 1.1.0
6879

6980
- Exception page (globalexception)

0 commit comments

Comments
 (0)