Skip to content

Commit 307a9b3

Browse files
huypubhuypub
authored
Merge pull request #103184 from MicrosoftDocs/master
2/03 PM Publish
2 parents b26872d + 81cb89e commit 307a9b3

File tree

139 files changed

+1909
-1407
lines changed

Some content is hidden

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

139 files changed

+1909
-1407
lines changed

‎.openpublishing.redirection.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -820,6 +820,16 @@
820820
"redirect_url": "/azure/cognitive-services//QnAMaker/Quickstarts/get-answer-from-knowledge-base-using-url-tool",
821821
"redirect_document_id": false
822822
},
823+
{
824+
"source_path": "articles/cognitive-services/LUIS/luis-tutorial-bot-csharp-appinsights.md",
825+
"redirect_url": "/azure/cognitive-services/LUIS/luis-csharp-tutorial-bf-v4",
826+
"redirect_document_id": false
827+
},
828+
{
829+
"source_path": "articles/cognitive-services/LUIS/luis-tutorial-bot-nodejs-appinsights.md",
830+
"redirect_url": "/azure/cognitive-services/LUIS/luis-nodejs-tutorial-bf-v4",
831+
"redirect_document_id": false
832+
},
823833
{
824834
"source_path": "articles/cognitive-services/LUIS/luis-tutorial-pattern-roles.md",
825835
"redirect_url": "/azure/cognitive-services/LUIS/luis-tutorial-pattern",

‎articles/active-directory-b2c/boolean-transformations.md

Lines changed: 39 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 09/10/2018
12+
ms.date: 02/03/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -110,6 +110,44 @@ The self-asserted technical profile calls the validation **login-NonInteractive*
110110
- **valueToCompareTo**: true
111111
- Result: Error thrown
112112

113+
## CompareBooleanClaimToValue
114+
115+
Checks that boolean value of a claims is equal to `true` or `false`, and return the result of the compression.
116+
117+
| Item | TransformationClaimType | Data Type | Notes |
118+
| ---- | ------------------------ | ---------- | ----- |
119+
| inputClaim | inputClaim | boolean | The ClaimType to be asserted. |
120+
| InputParameter |valueToCompareTo | boolean | The value to compare (true or false). |
121+
| OutputClaim | inputClaim | boolean | The ClaimType that is produced after this ClaimsTransformation has been invoked. |
122+
123+
124+
The following claims transformation demonstrates how to check the value of a boolean ClaimType with a `true` value. If the value of the `IsAgeOver21Years` ClaimType is equal to `true`, the claims transformation returns `true`, otherwise `false`.
125+
126+
```XML
127+
<ClaimsTransformation Id="AssertAccountEnabled" TransformationMethod="CompareBooleanClaimToValue">
128+
<InputClaims>
129+
<InputClaim ClaimTypeReferenceId="IsAgeOver21Years" TransformationClaimType="inputClaim" />
130+
</InputClaims>
131+
<InputParameters>
132+
<InputParameter Id="valueToCompareTo" DataType="boolean" Value="true" />
133+
</InputParameters>
134+
<OutputClaims>
135+
<OutputClaim ClaimTypeReferenceId="accountEnabled" TransformationClaimType="compareResult"/>
136+
</OutputClaims>
137+
</ClaimsTransformation>
138+
```
139+
140+
### Example
141+
142+
- Input claims:
143+
- **inputClaim**: false
144+
- Input parameters:
145+
- **valueToCompareTo**: true
146+
- Output claims:
147+
- **compareResult**: false
148+
149+
150+
113151
## NotClaims
114152

115153
Performs a Not operation of the boolean inputClaim and sets the outputClaim with result of the operation.
@@ -170,4 +208,3 @@ The following claims transformation demonstrates how to `Or` two boolean ClaimTy
170208
- **inputClaim2**: false
171209
- Output claims:
172210
- **outputClaim**: true
173-

‎articles/active-directory-b2c/date-transformations.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: celestedg
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: reference
11-
ms.date: 09/10/2018
11+
ms.date: 02/03/2020
1212
ms.author: marsma
1313
ms.subservice: B2C
1414
---
@@ -110,6 +110,35 @@ The following example demonstrates the conversion of the claim `dateOfBirth` (da
110110
- Output claims:
111111
- **outputClaim**: 1559347200 (June 1, 2019 12:00:00 AM)
112112

113+
## ConvertDateTimeToDateClaim
114+
115+
Converts a **DateTime** ClaimType to a **Date** ClaimType. The claims transformation removes the time format from the date.
116+
117+
| Item | TransformationClaimType | Data Type | Notes |
118+
| ---- | ----------------------- | --------- | ----- |
119+
| InputClaim | inputClaim | dateTime | The ClaimType to be converted. |
120+
| OutputClaim | outputClaim | date | The ClaimType that is produced after this ClaimsTransformation has been invoked. |
121+
122+
The following example demonstrates the conversion of the claim `systemDateTime` (dateTime data type) to another claim `systemDate` (date data type).
123+
124+
```XML
125+
<ClaimsTransformation Id="ConvertToDate" TransformationMethod="ConvertDateTimeToDateClaim">
126+
<InputClaims>
127+
<InputClaim ClaimTypeReferenceId="systemDateTime" TransformationClaimType="inputClaim" />
128+
</InputClaims>
129+
<OutputClaims>
130+
<OutputClaim ClaimTypeReferenceId="systemDate" TransformationClaimType="outputClaim" />
131+
</OutputClaims>
132+
</ClaimsTransformation>
133+
```
134+
135+
### Example
136+
137+
- Input claims:
138+
- **inputClaim**: 1559347200 (June 1, 2019 12:00:00 AM)
139+
- Output claims:
140+
- **outputClaim**: 2019-06-01
141+
113142
## GetCurrentDateTime
114143

115144
Get the current UTC date and time and add the value to a ClaimType.

‎articles/active-directory-b2c/general-transformations.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 08/27/2019
12+
ms.date: 02/03/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -20,6 +20,35 @@ ms.subservice: B2C
2020

2121
This article provides examples for using general claims transformations of the Identity Experience Framework schema in Azure Active Directory B2C (Azure AD B2C). For more information, see [ClaimsTransformations](claimstransformations.md).
2222

23+
## CopyClaim
24+
25+
Copy value of a claim to another. Both claims must be from the same type.
26+
27+
| Item | TransformationClaimType | Data Type | Notes |
28+
| ---- | ----------------------- | --------- | ----- |
29+
| InputClaim | inputClaim | string, int | The claim type which is to be copied. |
30+
| OutputClaim | outputClaim | string, int | The ClaimType that is produced after this ClaimsTransformation has been invoked. |
31+
32+
Use this claims transformation to copy a value from a string or numeric claim, to another claim. The following example copies the externalEmail claim value to email claim.
33+
34+
```XML
35+
<ClaimsTransformation Id="CopyEmailAddress" TransformationMethod="CopyClaim">
36+
<InputClaims>
37+
<InputClaim ClaimTypeReferenceId="externalEmail" TransformationClaimType="inputClaim"/>
38+
</InputClaims>
39+
<OutputClaims>
40+
<OutputClaim ClaimTypeReferenceId="email" TransformationClaimType="outputClaim"/>
41+
</OutputClaims>
42+
</ClaimsTransformation>
43+
```
44+
45+
### Example
46+
47+
- Input claims:
48+
- **inputClaim**: [email protected]
49+
- Output claims:
50+
- **outputClaim**: [email protected]
51+
2352
## DoesClaimExist
2453

2554
Checks if the **inputClaim** exists or not and sets **outputClaim** to true or false accordingly.

‎articles/active-directory-b2c/localization-string-ids.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: celestedg
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: reference
11-
ms.date: 01/31/2020
11+
ms.date: 02/03/2020
1212
ms.author: marsma
1313
ms.subservice: B2C
1414
---
@@ -212,7 +212,8 @@ The following are the IDs for a [Verification display control](display-control-v
212212
|verification_control_but_send_new_code |Send New Code |
213213
|verification_control_but_verify_code |Verify Code |
214214

215-
### Verification display control error messages
215+
## One time password error messages
216+
The following are the IDs for a [one time password technical profile](one-time-password-technical-profile.md) error messages
216217

217218
| ID | Default value |
218219
| -- | ------------- |

‎articles/active-directory-b2c/string-transformations.md

Lines changed: 116 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 09/10/2018
12+
ms.date: 02/03/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -588,3 +588,118 @@ For example, the following claims transformation checks if the value of **ageGro
588588
- **isMinorResponseCode**: B2C_V1_90001
589589
- **isMinor**: true
590590

591+
592+
## StringContains
593+
594+
Determine whether a specified substring occurs within the input claim. The result is a new boolean ClaimType with a value of `true` or `false`. `true` if the value parameter occurs within this string, otherwise, `false`.
595+
596+
| Item | TransformationClaimType | Data Type | Notes |
597+
| ---- | ----------------------- | --------- | ----- |
598+
| InputClaim | inputClaim | string | The claim type, which is to be searched. |
599+
|InputParameter|contains|string|The value to search.|
600+
|InputParameter|ignoreCase|string|Specifies whether this comparison should ignore the case of the string being compared.|
601+
| OutputClaim | outputClaim | string | The ClaimType that is produced after this ClaimsTransformation has been invoked. A boolean indicator if the substring occurs within the input claim. |
602+
603+
Use this claims transformation to check if a string claim type contains a substring. Following example, checks whether the `roles` string claim type contains the value of **admin**.
604+
605+
```XML
606+
<ClaimsTransformation Id="CheckIsAdmin" TransformationMethod="StringContains">
607+
<InputClaims>
608+
<InputClaim ClaimTypeReferenceId="roles" TransformationClaimType="inputClaim"/>
609+
</InputClaims>
610+
<InputParameters>
611+
<InputParameter Id="contains" DataType="string" Value="admin"/>
612+
<InputParameter Id="ignoreCase" DataType="string" Value="true"/>
613+
</InputParameters>
614+
<OutputClaims>
615+
<OutputClaim ClaimTypeReferenceId="isAdmin" TransformationClaimType="outputClaim"/>
616+
</OutputClaims>
617+
</ClaimsTransformation>
618+
```
619+
620+
### Example
621+
622+
- Input claims:
623+
- **inputClaim**: "Admin, Approver, Editor"
624+
- Input parameters:
625+
- **contains**: "admin,"
626+
- **ignoreCase**: true
627+
- Output claims:
628+
- **outputClaim**: true
629+
630+
## StringSubstring
631+
632+
Extracts parts of a string claim type, beginning at the character at the specified position, and returns the specified number of characters.
633+
634+
| Item | TransformationClaimType | Data Type | Notes |
635+
| ---- | ----------------------- | --------- | ----- |
636+
| InputClaim | inputClaim | string | The claim type, which contains the string. |
637+
| InputParameter | startIndex | int | The zero-based starting character position of a substring in this instance. |
638+
| InputParameter | length | int | The number of characters in the substring. |
639+
| OutputClaim | outputClaim | boolean | A string that is equivalent to the substring of length length that begins at startIndex in this instance, or Empty if startIndex is equal to the length of this instance and length is zero. |
640+
641+
For example, get the phone number country prefix.
642+
643+
644+
```XML
645+
<ClaimsTransformation Id="GetPhonePrefix" TransformationMethod="StringSubstring">
646+
<InputClaims>
647+
<InputClaim ClaimTypeReferenceId="phoneNumber" TransformationClaimType="inputClaim" />
648+
</InputClaims>
649+
<InputParameters>
650+
<InputParameter Id="startIndex" DataType="int" Value="0" />
651+
<InputParameter Id="length" DataType="int" Value="2" />
652+
</InputParameters>
653+
<OutputClaims>
654+
<OutputClaim ClaimTypeReferenceId="phonePrefix" TransformationClaimType="outputClaim" />
655+
</OutputClaims>
656+
</ClaimsTransformation>
657+
```
658+
### Example
659+
660+
- Input claims:
661+
- **inputClaim**: "+1644114520"
662+
- Input parameters:
663+
- **startIndex**: 0
664+
- **length**: 2
665+
- Output claims:
666+
- **outputClaim**: "+1"
667+
668+
## StringReplace
669+
670+
Searches a claim type string for a specified value, and returns a new claim type string in which all occurrences of a specified string in the current string are replaced with another specified string.
671+
672+
| Item | TransformationClaimType | Data Type | Notes |
673+
| ---- | ----------------------- | --------- | ----- |
674+
| InputClaim | inputClaim | string | The claim type, which contains the string. |
675+
| InputParameter | oldValue | string | The string to be searched. |
676+
| InputParameter | newValue | string | The string to replace all occurrences of `oldValue` |
677+
| OutputClaim | outputClaim | boolean | A string that is equivalent to the current string except that all instances of oldValue are replaced with newValue. If oldValue is not found in the current instance, the method returns the current instance unchanged. |
678+
679+
For example, normalize a phone number, by removing the `-` characters
680+
681+
682+
```XML
683+
<ClaimsTransformation Id="NormalizePhoneNumber" TransformationMethod="StringReplace">
684+
<InputClaims>
685+
<InputClaim ClaimTypeReferenceId="phoneNumber" TransformationClaimType="inputClaim" />
686+
</InputClaims>
687+
<InputParameters>
688+
<InputParameter Id="oldValue" DataType="string" Value="-" />
689+
<InputParameter Id="newValue" DataType="string" Value="" />
690+
</InputParameters>
691+
<OutputClaims>
692+
<OutputClaim ClaimTypeReferenceId="phoneNumber" TransformationClaimType="outputClaim" />
693+
</OutputClaims>
694+
</ClaimsTransformation>
695+
```
696+
### Example
697+
698+
- Input claims:
699+
- **inputClaim**: "+164-411-452-054"
700+
- Input parameters:
701+
- **oldValue**: "-"
702+
- **length**: ""
703+
- Output claims:
704+
- **outputClaim**: "+164411452054"
705+

‎articles/active-directory-b2c/stringcollection-transformations.md

Lines changed: 39 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 09/10/2018
12+
ms.date: 02/03/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -118,3 +118,41 @@ The following example reads the **otherMails** claim and return the first item i
118118
- Output claims:
119119
- **extractedItem**: "[email protected]"
120120

121+
122+
## StringCollectionContains
123+
124+
Checks if a StringCollection claim type contains an element
125+
126+
| Item | TransformationClaimType | Data Type | Notes |
127+
| ---- | ----------------------- | --------- | ----- |
128+
| InputClaim | inputClaim | stringCollection | The claim type which is to be searched. |
129+
|InputParameter|item|string|The value to search.|
130+
|InputParameter|ignoreCase|string|Specifies whether this comparison should ignore the case of the strings being compared.|
131+
| OutputClaim | outputClaim | boolean | The ClaimType that is produced after this ClaimsTransformation has been invoked. A boolean indicator if the collection contains such a string |
132+
133+
Following example checks whether the `roles` stringCollection claim type contains the value of **admin**.
134+
135+
```XML
136+
<ClaimsTransformation Id="IsAdmin" TransformationMethod="StringCollectionContains">
137+
<InputClaims>
138+
<InputClaim ClaimTypeReferenceId="roles" TransformationClaimType="inputClaim"/>
139+
</InputClaims>
140+
<InputParameters>
141+
<InputParameter Id="item" DataType="string" Value="Admin"/>
142+
<InputParameter Id="ignoreCase" DataType="string" Value="true"/>
143+
</InputParameters>
144+
<OutputClaims>
145+
<OutputClaim ClaimTypeReferenceId="isAdmin" TransformationClaimType="outputClaim"/>
146+
</OutputClaims>
147+
</ClaimsTransformation>
148+
```
149+
150+
- Input claims:
151+
- **inputClaim**: ["reader", "author", "admin"]
152+
- Input parameters:
153+
- **item**: "Admin"
154+
- **ignoreCase**: "true"
155+
- Output claims:
156+
- **outputClaim**: "true"
157+
158+

‎articles/active-directory/develop/media/howto-configure-publisher-domain/new-app-behavior-table.png

231 Bytes
Loading

‎articles/active-directory/develop/reply-url.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,11 @@ ms.reviewer: lenalepa, manrath
1616

1717
A redirect URI, or reply URL, is the location that the authorization server will send the user to once the app has been successfully authorized, and granted an authorization code or access token. The code or token is contained in the redirect URI or reply token so it's important that you register the correct location as part of the app registration process.
1818

19+
The following restrictions apply to reply URLs:
20+
21+
* The reply URL must begin with the scheme `https`.
22+
* The reply URL is case-sensitive. Its case must match the case of the URL path of your running application. For example, if your application includes as part of its path `.../abc/response-oidc`, do not specify `.../ABC/response-oidc` in the reply URL. Because the web browser treats paths as case-sensitive, cookies associated with `.../abc/response-oidc` may be excluded if redirected to the case-mismatched `.../ABC/response-oidc` URL.
23+
1924
## Maximum number of redirect URIs
2025

2126
The following table shows the maximum number of redirect URIs that you can add when you register your app.

‎articles/active-directory/saas-apps/media/wedo-tutorial/network-security-authentification.png

90.1 KB
Loading

0 commit comments

Comments
 (0)