Skip to content

Commit 5d716b2

Browse files
yoelhoryoelhor
committed
Acrolinx scorecard issues
1 parent ce04511 commit 5d716b2

10 files changed

+187
-147
lines changed

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

Lines changed: 25 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -9,29 +9,29 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 01/16/2022
12+
ms.date: 01/17/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
1616

1717
# Boolean claims transformations
1818

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

2121
## AndClaims
2222

23-
Performs an And operation of two boolean inputClaims and sets the outputClaim with result of the operation.
23+
Computes an `And` operation of two boolean input claims, and sets the output claim with result of the operation.
2424

25-
| Item | TransformationClaimType | Data Type | Notes |
25+
| Element | TransformationClaimType | Data Type | Notes |
2626
|-------| ------------------------ | ---------- | ----- |
27-
| InputClaim | inputClaim1 | boolean | The first ClaimType to evaluate. |
28-
| InputClaim | inputClaim2 | boolean | The second ClaimType to evaluate. |
29-
|OutputClaim | outputClaim | boolean | The ClaimTypes that will be produced after this claims transformation has been invoked (true or false). |
27+
| InputClaim | inputClaim1 | boolean | The first claim to evaluate. |
28+
| InputClaim | inputClaim2 | boolean | The second claim to evaluate. |
29+
|OutputClaim | outputClaim | boolean | The claim that will be produced after this claims transformation has been invoked (true or false). |
3030

3131

3232
### Example of AndClaims
3333

34-
The following claims transformation demonstrates how to And two boolean ClaimTypes: `isEmailNotExist`, and `isSocialAccount`. The output claim `presentEmailSelfAsserted` is set to `true` if the value of both input claims are `true`. In an orchestration step, you can use a precondition to preset a self-asserted page, only if a social account email is empty.
34+
The following claims transformation demonstrates how to `And` two boolean claims: `isEmailNotExist`, and `isSocialAccount`. The output claim `presentEmailSelfAsserted` is set to `true` if the values of both input claims are `true`.
3535

3636
```xml
3737
<ClaimsTransformation Id="CheckWhetherEmailBePresented" TransformationMethod="AndClaims">
@@ -56,9 +56,9 @@ The following claims transformation demonstrates how to And two boolean ClaimTyp
5656

5757
Checks that boolean values of two claims are equal, and throws an exception if they are not.
5858

59-
| Item | TransformationClaimType | Data Type | Notes |
59+
| Element | TransformationClaimType | Data Type | Notes |
6060
| ---- | ------------------------ | ---------- | ----- |
61-
| inputClaim | inputClaim | boolean | The ClaimType to be asserted. |
61+
| inputClaim | inputClaim | boolean | The claim to be checked. |
6262
| InputParameter |valueToCompareTo | boolean | The value to compare (true or false). |
6363

6464
The **AssertBooleanClaimIsEqualToValue** claims transformation is always executed from a [validation technical profile](validation-technical-profile.md) that is called by a [self-asserted technical profile](self-asserted-technical-profile.md). The **UserMessageIfClaimsTransformationBooleanValueIsNotEqual** self-asserted technical profile metadata controls the error message that the technical profile presents to the user. The error messages can be [localized](localization-string-ids.md#claims-transformations-error-messages).
@@ -67,7 +67,7 @@ The **AssertBooleanClaimIsEqualToValue** claims transformation is always execute
6767

6868
### Example of AssertBooleanClaimIsEqualToValue
6969

70-
The following claims transformation demonstrates how to check the value of a boolean ClaimType with a `true` value. If the value of the `accountEnabled` ClaimType is false, an error message is thrown.
70+
The following claims transformation demonstrates how to check the value of a boolean claim with a `true` value. If the value of the `accountEnabled` claim is false, an error message is thrown.
7171

7272
```xml
7373
<ClaimsTransformation Id="AssertAccountEnabledIsTrue" TransformationMethod="AssertBooleanClaimIsEqualToValue">
@@ -124,15 +124,15 @@ The self-asserted technical profile calls the validation `Example-AssertBoolean`
124124

125125
Checks that boolean value of a claim is equal to `true` or `false`, and return the result of the compression.
126126

127-
| Item | TransformationClaimType | Data Type | Notes |
127+
| Element | TransformationClaimType | Data Type | Notes |
128128
| ---- | ------------------------ | ---------- | ----- |
129-
| InputClaim | inputClaim | boolean | The ClaimType to be asserted. |
129+
| InputClaim | inputClaim | boolean | The claim to be compared. |
130130
| InputParameter |valueToCompareTo | boolean | The value to compare (true or false). |
131-
| OutputClaim | compareResult | boolean | The ClaimType that is produced after this ClaimsTransformation has been invoked. |
131+
| OutputClaim | compareResult | boolean | The claim that is produced after this claims transformation has been invoked. |
132132

133133
### Example of CompareBooleanClaimToValue
134134

135-
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`.
135+
The following claims transformation demonstrates how to check the value of a boolean claim with a `true` value. If the value of the `IsAgeOver21Years` claim is equal to `true`, the claims transformation returns `true`, otherwise `false`.
136136

137137
```xml
138138
<ClaimsTransformation Id="AssertAccountEnabled" TransformationMethod="CompareBooleanClaimToValue">
@@ -157,16 +157,16 @@ The following claims transformation demonstrates how to check the value of a boo
157157

158158
## NotClaims
159159

160-
Performs a Not operation of the boolean inputClaim and sets the outputClaim with result of the operation.
160+
Computes a `Not` operation of the boolean input claim and sets the output claim with result of the operation.
161161

162-
| Item | TransformationClaimType | Data Type | Notes |
162+
| Element | TransformationClaimType | Data Type | Notes |
163163
| ---- | ----------------------- | --------- | ----- |
164164
| InputClaim | inputClaim | boolean | The claim to be operated. |
165-
| OutputClaim | outputClaim | boolean | The ClaimTypes that are produced after this ClaimsTransformation has been invoked (true or false). |
165+
| OutputClaim | outputClaim | boolean | The claim that is produced after this claims transformation has been invoked (true or false). |
166166

167167
### Example of NotClaims
168168

169-
The following claim transformation demonstrates how to perform logical negation on a claim.
169+
The following claims transformation demonstrates how to perform logical negation on a claim.
170170

171171
```xml
172172
<ClaimsTransformation Id="CheckWhetherEmailBePresented" TransformationMethod="NotClaims">
@@ -186,17 +186,17 @@ The following claim transformation demonstrates how to perform logical negation
186186

187187
## OrClaims
188188

189-
Computes an Or of two boolean inputClaims and sets the outputClaim with result of the operation.
189+
Computes an `Or` of two boolean claims and sets the output claim with result of the operation.
190190

191-
| Item | TransformationClaimType | Data Type | Notes |
191+
| Element | TransformationClaimType | Data Type | Notes |
192192
| ---- | ----------------------- | --------- | ----- |
193-
| InputClaim | inputClaim1 | boolean | The first ClaimType to evaluate. |
194-
| InputClaim | inputClaim2 | boolean | The second ClaimType to evaluate. |
195-
| OutputClaim | outputClaim | boolean | The ClaimTypes that will be produced after this ClaimsTransformation has been invoked (true or false). |
193+
| InputClaim | inputClaim1 | boolean | The first claim to evaluate. |
194+
| InputClaim | inputClaim2 | boolean | The second claim to evaluate. |
195+
| OutputClaim | outputClaim | boolean | The claim that will be produced after this claims transformation has been invoked (true or false). |
196196

197197
### Example of OrClaims
198198

199-
The following claims transformation demonstrates how to `Or` two boolean ClaimTypes. In the orchestration step, you can use a precondition to preset a self-asserted page, if the value of one of the claims is `true`.
199+
The following claims transformation demonstrates how to `Or` two boolean claims.
200200

201201
```xml
202202
<ClaimsTransformation Id="CheckWhetherEmailBePresented" TransformationMethod="OrClaims">

‎articles/active-directory-b2c/claims-transformation-technical-profile.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
2-
title: Define a Claims transformation technical profile
2+
title: Define a claims transformation technical profile
33
titleSuffix: Azure AD B2C
4-
description: Define a Claims transformation technical profile in a custom policy in Azure Active Directory B2C.
4+
description: Define a claims transformation technical profile in a custom policy in Azure Active Directory B2C.
55
services: active-directory-b2c
66
author: kengaderdus
77
manager: CelesteDG
88

99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 01/16/2022
12+
ms.date: 01/17/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
@@ -35,7 +35,7 @@ The following example shows a claims transformation technical profile:
3535

3636
## Output claims
3737

38-
The **OutputClaims** element is mandatory. You should provide at least one output claim returned by the technical profile. The following example shows how to set default values in the output claims:
38+
The **OutputClaims** element is mandatory. Provide at least one output claim returned by the technical profile. The following example shows how to set default values in the output claims:
3939

4040
```xml
4141
<OutputClaims>
@@ -78,7 +78,7 @@ TransformationClaimType="collection" />
7878
</TechnicalProfile>
7979
```
8080

81-
The claims transformation technical profile enables you to execute a claims transformation from any user journey's orchestration step. In the following example, the orchestration step calls one of the unlink technical profiles, such as **UnLink-Facebook-OAUTH**. This technical profile calls the claims transformation technical profile **RemoveAlternativeSecurityIdByIdentityProvider**, which generates a new **AlternativeSecurityIds2** claim that contains the list of user social identities, while removing the Facebook identity from the collections.
81+
The claims transformation technical profile enables you to execute a claims transformation from any user journey's orchestration step. In the following example, the orchestration step calls one of the unlink technical profiles, such as **UnLink-Facebook-OAUTH**. This technical profile calls the output claims transformation **RemoveAlternativeSecurityIdByIdentityProvider**, which generates a new **AlternativeSecurityIds2** claim. The output claim contains the list of user's social identities, while removing the Facebook identity from the collections.
8282

8383
```xml
8484
<UserJourney Id="AccountUnLink">
@@ -100,8 +100,8 @@ The claims transformation technical profile enables you to execute a claims tran
100100

101101
| Attribute | Required | Description |
102102
| --------- | -------- | ----------- |
103-
| IncludeClaimResolvingInClaimsHandling | No | For input and output claims, specifies whether [claims resolution](claim-resolver-overview.md) is included in the technical profile. Possible values: `true`, or `false` (default). If you want to use a claims resolver in the technical profile, set this to `true`. |
104-
| ContentDefinitionReferenceId | No | The identifier of the [content definition](contentdefinitions.md) associated with this technical profile. The content definition metadata is required for [FormatLocalizedString](string-transformations.md#formatlocalizedstring) , [GetLocalizedStringsTransformation](string-transformations.md#getlocalizedstringstransformation), and [GetMappedValueFromLocalizedCollection](string-transformations.md#getmappedvaluefromlocalizedcollection) claims transformations.|
103+
| IncludeClaimResolvingInClaimsHandling | No | For input and output claims, specifies whether [claims resolution](claim-resolver-overview.md) is included in the technical profile. Possible values: `true`, or `false` (default). If you want to use a claims resolver in the technical profile, set this metadata to `true`. |
104+
| ContentDefinitionReferenceId | No | The identifier of the [content definition](contentdefinitions.md) associated with this technical profile. The content definition metadata is required for [FormatLocalizedString](string-transformations.md#formatlocalizedstring), [GetLocalizedStringsTransformation](string-transformations.md#getlocalizedstringstransformation), and [GetMappedValueFromLocalizedCollection](string-transformations.md#getmappedvaluefromlocalizedcollection) claims transformations.|
105105

106106
## Use a validation technical profile
107107

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

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -8,21 +8,21 @@ manager: CelesteDG
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: reference
11-
ms.date: 1/16/2022
11+
ms.date: 1/17/2022
1212
ms.author: kengaderdus
1313
ms.subservice: B2C
1414
ms.custom: "b2c-support"
1515
---
1616

1717
# Date claims transformations
1818

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

2121
## AssertDateTimeIsGreaterThan
2222

2323
Asserts that one date is later than a second date. Determines whether the `rightOperand` is greater than the `leftOperand`. If yes, throws an exception.
2424

25-
| Item | TransformationClaimType | Data Type | Notes |
25+
| Element | TransformationClaimType | Data Type | Notes |
2626
| ---- | ----------------------- | --------- | ----- |
2727
| InputClaim | leftOperand | string | First claim's type, which should be later than the second claim. |
2828
| InputClaim | rightOperand | string | Second claim's type, which should be earlier than the first claim. |
@@ -104,7 +104,7 @@ The self-asserted technical profile calls the validation `Example-AssertDates` t
104104

105105
Converts a `DateTime` claim type to a `Date` claim type. The claims transformation removes the time format from the date.
106106

107-
| Item | TransformationClaimType | Data Type | Notes |
107+
| Element | TransformationClaimType | Data Type | Notes |
108108
| ---- | ----------------------- | --------- | ----- |
109109
| InputClaim | inputClaim | dateTime | The claim type to be converted. |
110110
| OutputClaim | outputClaim | date | The claim type that is produced after this claims transformation has been invoked. |
@@ -133,7 +133,7 @@ The following example demonstrates the conversion of the claim `systemDateTime`
133133

134134
Converts a `Date` claim type to a `DateTime` claim type. The claims transformation converts the time format and adds 12:00:00 AM to the date.
135135

136-
| Item | TransformationClaimType | Data Type | Notes |
136+
| Element | TransformationClaimType | Data Type | Notes |
137137
| ---- | ----------------------- | --------- | ----- |
138138
| InputClaim | inputClaim | date | The claim type to be converted. |
139139
| OutputClaim | outputClaim | dateTime | The claim type that is produced after this claims transformation has been invoked. |
@@ -162,20 +162,17 @@ The following example demonstrates the conversion of the claim `dateOfBirth` (da
162162

163163
Compares two dates and determines whether the first date is later, earlier, or equal to another. The result is a new Boolean claim with a value of `true` or `false`.
164164

165-
| Item | TransformationClaimType | Data Type | Notes |
165+
| Element | TransformationClaimType | Data Type | Notes |
166166
| ---- | ----------------------- | --------- | ----- |
167167
| InputClaim | firstDateTime | dateTime | The first date to compare whether it's later, earlier, or equal to the second date. Null value throws an exception. |
168-
| InputClaim | secondDateTime | dateTime | The second date to compare. Null value is treated as the current datetTime. |
168+
| InputClaim | secondDateTime | dateTime | The second date to compare. Null value is treated as the current date and time. |
169169
| InputParameter | timeSpanInSeconds | int | Timespan to add to the first date. Possible values: range from negative -2,147,483,648 through positive 2,147,483,647. |
170-
| InputParameter | operator | string | One of following values: same, later than, or earlier than. |
170+
| InputParameter | operator | string | One of following values: `same`, `later than`, or `earlier than`. |
171171
| OutputClaim | result | boolean | The claim that is produced after this claims transformation has been invoked. |
172172

173-
Use this claims transformation to determine if first date plus the timespan parameter is later, earlier, or equal to another. For example, you may store the last time a user accepted your terms of services (TOS). After three months, you can ask the user to access the TOS again.
174-
To run the claim transformation, you first need to get the current date and also the last time user accepts the TOS.
175-
176173
### Example of DateTimeComparison
177174

178-
The following example shows that the first date (2022-01-01T00:00:00) plus 90 days is later than the second date (2022-03-16T00:00:00).
175+
Use this claims transformation to determine if first date plus the `timeSpanInSeconds` parameter is later, earlier, or equal to another. The following example shows that the first date (2022-01-01T00:00:00) plus 90 days is later than the second date (2022-03-16T00:00:00).
179176

180177
```xml
181178
<ClaimsTransformation Id="CompareLastTOSAcceptedWithCurrentDateTime" TransformationMethod="DateTimeComparison">
@@ -206,7 +203,7 @@ The following example shows that the first date (2022-01-01T00:00:00) plus 90 da
206203

207204
Get the current UTC date and time and add the value to a claim type.
208205

209-
| Item | TransformationClaimType | Data Type | Notes |
206+
| Element | TransformationClaimType | Data Type | Notes |
210207
| ---- | ----------------------- | --------- | ----- |
211208
| OutputClaim | currentDateTime | dateTime | The claim type that is produced after this claims transformation has been invoked. |
212209

0 commit comments

Comments
 (0)