-
Notifications
You must be signed in to change notification settings - Fork 356
Fix: Clarify reCAPTCHA validation applies to first-factor authenticators (Product IS issue #25944) #5614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Fix: Clarify reCAPTCHA validation applies to first-factor authenticators (Product IS issue #25944) #5614
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,21 +18,21 @@ | |
|
||
WSO2 Identity Server 7.1.0 introduces **AI LoginFlow** and **AI Branding**, bringing automation and intelligence to identity and access management. Previously, administrators had to manually configure authentication sequences and customize login pages, a process that was often time-consuming and prone to errors. With AI LoginFlow and AI Branding, WSO2 Identity Server 7.1.0 leverages AI-driven natural language inputs to simplify these tasks, reducing manual effort while minimizing configuration errors. These features enhance both user and administrator experiences by streamlining authentication setup and branding customization. | ||
|
||
- **AI LoginFlow** - Lets administrators define authentication flows using natural language, simplifying complex configurations and reducing setup effort. Learn more about [AI LoginFlow]({{base_path}}/guides/authentication/login-flow-ai/). | ||
Check failure on line 21 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
|
||
- **AI Branding** - Allows administrators to customize login pages using natural language, making it easy to create designs that match their organization's identity. Learn more about [AI Branding]({{base_path}}/guides/branding/branding-ai/). | ||
Check failure on line 23 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
|
||
- **Custom Authentication Service Extension** | ||
|
||
Check failure on line 26 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
Administrators can now extend authentication capabilities by implementing custom authentication services. This enhancement offers greater flexibility in addressing diverse authentication requirements beyond the built-in authenticators. | ||
|
||
- **Pre-Issue Access Token Service Extension** | ||
Check failure on line 29 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
|
||
Check failure on line 30 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
Supports executing custom logic before issuing an access token, providing greater flexibility in the OAuth2 token issuance process. This enhancement allows administrators to, | ||
|
||
Check failure on line 32 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
- Add, modify, or remove scopes. | ||
Check failure on line 33 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
- Add, modify, or remove audience values. | ||
Check failure on line 34 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
- Modify or remove user attributes incorporated into the access token. | ||
Check failure on line 35 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
- Add custom claims (only string, number, boolean, and string type arrays are allowed). | ||
- Update the validity period of the access token. | ||
|
||
|
@@ -289,9 +289,13 @@ | |
|
||
For backward compatibility, the `internal_bulk_resource_create scope` still supported and allows performing any operation through the bulk endpoint. | ||
|
||
- **Enabled reCAPTCHA validation for local Email/SMS OTP authenticators** | ||
|
||
reCAPTCHA validation is now enabled for local Email/SMS OTP authenticators when they are used as first-factor authenticators. | ||
Check warning on line 294 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
|
||
## Deprecated features | ||
|
||
In WSO2 Identity Server 7.1.0, we have deprecated several features to enhance security, streamline operations, and improve overall usability. These deprecations align with our commitment to maintaining a robust and future-ready platform. Below is a list of deprecated features along with recommended actions for users. Learn more about [WSO2 Identity Server Feature Deprecation]({{base_path}}/references/wso2-identity-server-feature-deprecation/). | ||
Check warning on line 298 in en/identity-server/next/docs/get-started/about-this-release.md
|
||
|
||
- **Password Expiring User Identification Rest API** | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the linked issue is about updating migration docs, not public documentation