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-b2c/add-captcha.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,15 +11,15 @@ ms.author: kengaderdus
11
11
ms.subservice: B2C
12
12
zone_pivot_groups: b2c-policy-type
13
13
14
-
#Customer intent: As a developer, I want to enable CAPTCHA in consumer-facing application that is secured by Azure Active Directory B2C.
14
+
#Customer intent: As a developer, I want to enable CAPTCHA in consumer-facing application that is secured by Azure Active Directory B2C, so that I can protect my sign-in and sign-up flows from automated attacks.
Azure Active Directory B2C (Azure AD B2C) allows you to enable CAPTCHA prevent to automated attacks on your consumer-facing applications. Azure AD B2C’s CAPTCHA supports both audio and visual captcha challenges. You can enable this security feature in both sign-up and sign-in flows for your local accounts. CAPTCHA isn't applicable for social identity providers' sign-in.
22
+
Azure Active Directory B2C (Azure AD B2C) allows you to enable CAPTCHA prevent to automated attacks on your consumer-facing applications. Azure AD B2C’s CAPTCHA supports both audio and visual CAPTCHA challenges. You can enable this security feature in both sign-up and sign-in flows for your local accounts. CAPTCHA isn't applicable for social identity providers' sign-in.
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/captcha-technical-profile.md
+26-22Lines changed: 26 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Define a CAPTCHA technical profile in a custom policy
3
3
titleSuffix: Azure AD B2C
4
-
description: Define a captcha technical profile custom policy in Azure Active Directory B2C.
4
+
description: Define a CAPTCHA technical profile custom policy in Azure Active Directory B2C.
5
5
6
6
author: kengaderdus
7
7
manager: mwongerapk
@@ -13,18 +13,18 @@ ms.date: 01/17/2024
13
13
ms.author: kengaderdus
14
14
ms.subservice: B2C
15
15
16
-
#Customer intent: As a developer integrating a customer-facing application with Azure Active Directory B2C, I want to define a CAPTCHA technical profile, so that I can secure sign-up and sign-in flows from automated attacks.
16
+
#Customer intent: As a developer integrating a customer-facing application with Azure AD B2C, I want to define a CAPTCHA technical profile, so that I can secure sign-up and sign-in flows from automated attacks.
17
17
---
18
18
19
19
# Define a CAPTCHA technical profile in an Azure Active Directory B2C custom policy
A Completely Automated Public Turing Tests to Tell Computer and Human Apart (CAPTCHA) technical profiles enables Azure Active Directory B2C (Azure AD B2C) to prevent automated attacks. Azure AD B2C's CAPTCHA technical profiles supports both audio and visual captcha challenges types.
23
+
A Completely Automated Public Turing Tests to Tell Computer and Human Apart (CAPTCHA) technical profiles enables Azure Active Directory B2C (Azure AD B2C) to prevent automated attacks. Azure AD B2C's CAPTCHA technical profile supports both audio and visual CAPTCHA challenges types.
24
24
25
25
## Protocol
26
26
27
-
The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly that is used by Azure AD B2C, for captcha:
27
+
The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly that is used by Azure AD B2C, for CAPTCHA:
@@ -41,13 +41,13 @@ The following example shows a self-asserted technical profile for email sign-up:
41
41
42
42
CAPTCHA technical profile operations has two operations:
43
43
44
-
-**Get challenge operation** generates the captcha code string, then displays it on the user interface by using a [captcha display control](display-control-captcha.md). The display includes an input textbox. This operation directs the user to input the characters they see or hear into the input textbox. The user can switch between visual and audio challenge types as needed.
44
+
-**Get challenge operation** generates the CAPTCHA code string, then displays it on the user interface by using a [CAPTCHA display control](display-control-captcha.md). The display includes an input textbox. This operation directs the user to input the characters they see or hear into the input textbox. The user can switch between visual and audio challenge types as needed.
45
45
46
46
-**Verify code operation** verifies the characters input by the user.
47
47
48
48
## Get challenge
49
49
50
-
The first operation generates the captcha code string, then displays it on the user interface.
50
+
The first operation generates the CAPTCHA code string, then displays it on the user interface.
51
51
52
52
### Input claims
53
53
@@ -60,7 +60,7 @@ The **InputClaims** element contains a list of claims to send to Azure AD B2C's
60
60
61
61
### Display claims
62
62
63
-
The **DisplayClaims** element contains a list of claims to be presented on the screen for the user to see. For example, the user is presented with the captcha challenge code to read.
63
+
The **DisplayClaims** element contains a list of claims to be presented on the screen for the user to see. For example, the user is presented with the CAPTCHA challenge code to read.
64
64
65
65
| ClaimReferenceId | Required | Description |
66
66
| --------- | -------- | ----------- |
@@ -69,7 +69,7 @@ The **DisplayClaims** element contains a list of claims to be presented on the s
69
69
70
70
### Output claims
71
71
72
-
The **OutputClaims** element contains a list of claims returned by the captcha technical profile.
72
+
The **OutputClaims** element contains a list of claims returned by the CAPTCHA technical profile.
73
73
74
74
| ClaimReferenceId | Required | Description |
75
75
| --------- | -------- | ----------- |
@@ -84,9 +84,9 @@ The **OutputClaims** element contains a list of claims returned by the captcha t
84
84
| Operation | Yes | Value must be *GetChallenge*.|
85
85
| Brand | Yes | Value must be *HIP*.|
86
86
87
-
### Example: Generate captcha code
87
+
### Example: Generate CAPTCHA code
88
88
89
-
The following example shows a captcha technical profile that is used to generate a code:
89
+
The following example shows a CAPTCHA technical profile that you use to generate a code:
90
90
91
91
```xml
92
92
<TechnicalProfileId="HIP-GetChallenge">
@@ -116,9 +116,9 @@ The following example shows a captcha technical profile that is used to generate
116
116
```
117
117
118
118
119
-
## Verify code
119
+
## Verify challenge
120
120
121
-
The second operation verifies the captcha code.
121
+
The second operation verifies the CAPTCHA challenge.
122
122
123
123
### Input claims
124
124
@@ -127,9 +127,9 @@ The **InputClaims** element contains a list of claims to send to Azure AD B2C's
127
127
| ClaimReferenceId | Required | Description |
128
128
| --------- | -------- | ----------- |
129
129
| challengeType | No | The CAPTCHA challenge type, Audio or Visual (default).|
130
-
|challengeId|||
131
-
|captchaEntered|||
132
-
|azureregion|||
130
+
|challengeId|Yes | A unique identifier for CAPTCHA used for session verification. Populated from the *GetChallenge* call. |
131
+
|captchaEntered|Yes | The challenge code that the user inputs into the challenge textbox on the user interface. |
132
+
|azureregion|Yes | The service region that will serve the CAPTCHA challenge request. Populated from the *GetChallenge* call.|
133
133
134
134
135
135
### Display claims
@@ -138,27 +138,27 @@ The **DisplayClaims** element contains a list of claims to be presented on the s
138
138
139
139
| ClaimReferenceId | Required | Description |
140
140
| --------- | -------- | ----------- |
141
-
| captchaEntered || The CAPTCHA code entered by the user.|
141
+
| captchaEntered |Yes| The CAPTCHA challenge code entered by the user.|
142
142
143
143
### Output claims
144
144
145
145
The **OutputClaims** element contains a list of claims returned by the captcha technical profile.
146
146
147
147
| ClaimReferenceId | Required | Description |
148
148
| --------- | -------- | ----------- |
149
-
| challengeId || A unique identifier for CAPTCHA challenge code.|
150
-
| isCaptchaSolved || A flag indicating whether the captcha challenge was successfully solved.|
151
-
| reason | Yes ||
149
+
| challengeId |Yes| A unique identifier for CAPTCHA used for session verification.|
150
+
| isCaptchaSolved |Yes| A flag indicating whether the CAPTCHA challenge is successfully solved.|
151
+
| reason | Yes |Used to communicate to the user whether the attempt to solve the challenge is successful or not. |
152
152
153
153
### Metadata
154
154
| Attribute | Required | Description |
155
155
| --------- | -------- | ----------- |
156
156
| Operation | Yes | Value must be **VerifyChallenge**.|
157
157
| Brand | Yes | Value must be **HIP**.|
158
158
159
-
### Example: Verify captcha code
159
+
### Example: Verify CAPTCHA code
160
160
161
-
The following example shows a captcha technical profile that is used to verify a captcha code:
161
+
The following example shows a CAPTCHA technical profile that you use to verify a CAPTCHA code:
162
162
163
163
```xml
164
164
<TechnicalProfileId="HIP-VerifyChallenge">
@@ -187,4 +187,8 @@ The following example shows a captcha technical profile that is used to verify a
187
187
</OutputClaims>
188
188
189
189
</TechnicalProfile>
190
-
```
190
+
```
191
+
192
+
## Next steps
193
+
194
+
-[Enable CAPTCHA in Azure Active Directory B2C](add-captcha.md).
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/display-control-captcha.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,16 +13,16 @@ ms.date: 01/17/2024
13
13
ms.author: kengaderdus
14
14
ms.subservice: B2C
15
15
16
-
#Customer intent: As a developer integrating customer-facing apps with Azure AD B2C, I want to learn how to define a CAPTCHA display control so that I can enable CAPTCHA in my authentication using Azure AD B2C's custom policies.
16
+
#Customer intent: As a developer integrating customer-facing apps with Azure AD B2C, I want to learn how to define a CAPTCHA display control for Azure AD B2C's custom policies so that I can protect my authentication flows from automated attacks.
17
17
---
18
18
19
19
# Verify CAPTCHA challenge string using CAPTCHA display control
20
20
21
-
Use CAPTCHA display controls to generate a captcha challenge string, then verify it by asking the user to enter what they see or hear. To display a CAPTCHA display control, you reference it from a [self-asserted technical profile](self-asserted-technical-profile.md), and you must set the self-asserted technical profile's `setting.enableCaptchaChallenge` metadata value to *true*.
21
+
Use CAPTCHA display controls to generate a CAPTCHA challenge string, then verify it by asking the user to enter what they see or hear. To display a CAPTCHA display control, you reference it from a [self-asserted technical profile](self-asserted-technical-profile.md), and you must set the self-asserted technical profile's `setting.enableCaptchaChallenge` metadata value to *true*.
22
22
23
23
The screenshot shows the CAPTCHA display control shown on a sign-up page:
24
24
25
-
:::image type="content" source="media/add-captcha/add-captcha.png" alt-text="Screenshot of captcha as it appears in the sign up page.":::
25
+
:::image type="content" source="media/add-captcha/add-captcha.png" alt-text="Screenshot of CAPTCHA as it appears in the sign up page.":::
26
26
27
27
The sign-up page loads with the CAPTCHA display control. The user then inputs the characters they see or hear. The **Send verification code** button sends a verification code to the user's email, and isn't CAPTCHA display control element, but it causes the CAPTCHA challenge string to be verified.
28
28
@@ -33,10 +33,10 @@ This table summarizes the elements that a CAPTCHA display control contains.
33
33
| Element | Required | Description |
34
34
| --------- | -------- | ----------- |
35
35
| UserInterfaceControlType | Yes | Value must be *CaptchaControl*.|
36
-
| InputClaims | Yes | One or more claims required as input to specify the captcha challenge type and to uniquely identify the challenge. |
37
-
| DisplayClaims | Yes | The claims to be shown to the user such as the captcha challenge code, or collected from the user, such as code input by the user |
38
-
| OutputClaim | No | Any claim to be returned to the self-asserted page after the user completes captcha code verification process. |
39
-
| Actions | Yes | CAPTCHA display control contains two actions, *GetChallenge* and *VerifyChallenge*. <br> *GetChallenge* action generates, then displays a captcha challenge code on the user interface. <br> *VerifyChallenge* action verifies the CAPTCHA challenge code that the user inputs. |
36
+
| InputClaims | Yes | One or more claims required as input to specify the CAPTCHA challenge type and to uniquely identify the challenge. |
37
+
| DisplayClaims | Yes | The claims to be shown to the user such as the CAPTCHA challenge code, or collected from the user, such as code input by the user |
38
+
| OutputClaim | No | Any claim to be returned to the self-asserted page after the user completes CAPTCHA code verification process. |
39
+
| Actions | Yes | CAPTCHA display control contains two actions, *GetChallenge* and *VerifyChallenge*. <br> *GetChallenge* action generates, then displays a CAPTCHA challenge code on the user interface. <br> *VerifyChallenge* action verifies the CAPTCHA challenge code that the user inputs. |
40
40
41
41
The following XML snippet code shows an examples of CaptchaProvider display control:
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/localization-string-ids.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: CelesteDG
8
8
ms.service: active-directory
9
9
10
10
ms.topic: reference
11
-
ms.date: 01/11/2024
11
+
ms.date: 01/17/2024
12
12
ms.author: kengaderdus
13
13
ms.subservice: B2C
14
14
@@ -657,7 +657,7 @@ The following IDs are used for a [CAPTCHA display control](display-control-captc
657
657
|`charsnotmatched_error`| The characters did not match for CAPTCHA challenge. Please try again | The message to display to the user if they enter a wrong CAPTCHA code. |
658
658
|`api_error`| Api error on CAPTCHA control | The message to display to the user if an error occurs while Azure AD B2C attempts to validate the CAPTCHA code. |
659
659
|`captcha_resolved`| Success! | The message to display to the user if they enter a correct CAPTCHA code. |
660
-
|`DisplayName`| Help us beat the bots. | The CAPTCHA display control display name. |
660
+
|`DisplayName`| Help us beat the bots. | The CAPTCHA display control's display name. |
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/self-asserted-technical-profile.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,13 +9,13 @@ manager: CelesteDG
9
9
ms.service: active-directory
10
10
11
11
ms.topic: reference
12
-
ms.date: 01/11/2024
12
+
ms.date: 01/17/2024
13
13
14
14
ms.author: kengaderdus
15
15
ms.subservice: B2C
16
16
17
17
18
-
#Customer intent: As a developer using Azure Active Directory B2C, I want to define a self-asserted technical profile with display claims and output claims, so that I can collect and validate user input and return the claims to the next orchestration step.
18
+
#Customer intent: As a developer using Azure Active Directory B2C, I want to define a self-asserted technical profile with display, so that I can collect and validate user input.
0 commit comments