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
+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
@@ -293,7 +293,7 @@ To enable CAPTCHA in MFA flow, you need to make an update in two technical profi
293
293
294
294
1. Inspect your sign-up sign-in user journey, such as *SignUpOrSignIn*, to identify the self-asserted technical profile and phone factor technical profiles that are responsible for your sign-up or sign-in flow.
295
295
296
-
1. In both of the technical profiles, add a metadata key and a display claim entries as shown in the following code:
296
+
1. In both of the technical profiles, add a metadata key and a display claim entry as shown in the following code:
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/captcha-technical-profile.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ The following example shows a self-asserted technical profile for email sign-up:
39
39
```
40
40
## CAPTCHA technical profile operations
41
41
42
-
CAPTCHA technical profile operations has two operations:
42
+
CAPTCHA technical profile operations have two operations:
43
43
44
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
@@ -51,12 +51,12 @@ The first operation generates the CAPTCHA code string, then displays it on the u
51
51
52
52
### Input claims
53
53
54
-
The **InputClaims** element contains a list of claims to send to Azure AD B2C's capt service.
54
+
The **InputClaims** element contains a list of claims to send to Azure AD B2C's CAPTCHA service.
55
55
56
56
| ClaimReferenceId | Required | Description |
57
57
| --------- | -------- | ----------- |
58
58
| challengeType | No | The CAPTCHA challenge type, Audio or Visual (default).|
59
-
| azureregion | Yes | The service region that will serve the CAPTCHA challenge request. |
59
+
| azureregion | Yes | The service region that serves the CAPTCHA challenge request. |
60
60
61
61
### Display claims
62
62
@@ -75,7 +75,7 @@ The **OutputClaims** element contains a list of claims returned by the CAPTCHA t
75
75
| --------- | -------- | ----------- |
76
76
| challengeId | Yes | A unique identifier for CAPTCHA challenge code.|
77
77
| challengeString | Yes | The CAPTCHA challenge code.|
78
-
| azureregion | Yes | The service region that will serve the CAPTCHA challenge request.|
78
+
| azureregion | Yes | The service region that serves the CAPTCHA challenge request.|
79
79
80
80
81
81
### Metadata
@@ -122,14 +122,14 @@ The second operation verifies the CAPTCHA challenge.
122
122
123
123
### Input claims
124
124
125
-
The **InputClaims** element contains a list of claims to send to Azure AD B2C's capt service.
125
+
The **InputClaims** element contains a list of claims to send to Azure AD B2C's CAPTCHA service.
126
126
127
127
| ClaimReferenceId | Required | Description |
128
128
| --------- | -------- | ----------- |
129
129
| challengeType | No | The CAPTCHA challenge type, Audio or Visual (default).|
130
130
|challengeId| Yes | A unique identifier for CAPTCHA used for session verification. Populated from the *GetChallenge* call. |
131
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.|
132
+
|azureregion| Yes | The service region that serves the CAPTCHA challenge request. Populated from the *GetChallenge* call.|
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/display-control-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
@@ -22,7 +22,7 @@ Use CAPTCHA display controls to generate a CAPTCHA challenge string, then verify
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 signup 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
@@ -38,7 +38,7 @@ This table summarizes the elements that a CAPTCHA display control contains.
38
38
| OutputClaim | No | Any claim to be returned to the self-asserted page after the user completes CAPTCHA code verification process. |
39
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
-
The following XML snippet code shows an examples of CaptchaProvider display control:
41
+
The following XML snippet code shows an example of CaptchaProvider display control:
0 commit comments