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: en/identity-server/next/docs/get-started/about-this-release.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,11 +22,13 @@ With these building blocks, you can create flexible, secure, and user-friendly f
22
22
23
23
The flow builder supports the following use cases:
24
24
25
-
-**Self-registration** - Design custom self-registration flows with multiple steps, conditional logic, and data collection. Learn about building a [self-registration flow using the flow builder]({{base_path}}/guides/flows/self-registration/).
25
+
-**Self-registration** - Design custom self-registration flows with multiple steps, conditional logic, and data collection.
26
26
27
-
-**Password recovery** - Create tailored password recovery experiences with identity verification and secure reset options. Learn about building a [password recovery flow using the flow builder]({{base_path}}/guides/flows/password-recovery/).
27
+
-**Password recovery** - Create tailored password recovery experiences with identity verification and secure reset options.
28
28
29
-
-**Invited user registration** - Build invitation-based registration flows that collect necessary information and set up user accounts. Learn about building an [invited user registration flow using the flow builder]({{base_path}}/guides/flows/invited-user-registration/).
29
+
-**Invited user registration** - Build invitation-based registration flows that collect necessary information and set up user accounts.
30
+
31
+
Learn more about [Flows]({{base_path}}/guides/flows/).
30
32
31
33
### AI agent identity management
32
34
@@ -430,7 +432,7 @@ This separation provides a clear distinction between the organization’s identi
430
432
431
433
### Legacy user registration and management flows
432
434
433
-
Previously, WSO2 Identity Server offered built-in flows for user registration and management that provided basic functionality and limited customization options. These are
435
+
Previously, WSO2 Identity Server offered built-in flows for user registration and management that provided basic functionality and limited customization options.
434
436
435
437
These flows are now deprecated and replaced with the new **Flow Builder**, which offers a more flexible and powerful way to design and manage user registration and management journeys.
Copy file name to clipboardExpand all lines: en/includes/guides/users/onboard-users.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ You can use one of the following methods to onboard users to your organization i
4
4
5
5
- The user can self-register via the My Account portal or the login page of an application if self-registration is enabled in the organization. Learn how to [configure self-registration]({{base_path}}/guides/account-configurations/user-onboarding/self-registration/).
6
6
7
-
- An administrator can onboard users from a secondary user store by [configuring a secondary user store in {{product_name}}]({{base_path}}/guides/users/user-stores/configure-secondary-user-stores/).
7
+
- An administrator can onboard users from a secondary user store by [configuring a secondary user store in {{product_name}}]({{base_path}}/guides/users/user-stores/configure-a-user-store/).
8
8
9
9
!!! note
10
10
If the secondary user store access type is read-only, you cannot update the user profiles of users onboarded from this read-only user store.
@@ -21,8 +21,10 @@ Let's look at how administrators can onboard users from the {{ product_name }} C
- The user's username is always unique to the organization and you can't change the username once it is created.
24
+
{% if product_name == "WSO2 Identiy Server" %}-{% endif %} The user's username is always unique to the organization and you can't change the username once it is created.
25
+
{% if product_name == "WSO2 Identity Server "%}
25
26
- Optionally, you can [configure email address as the username]({{base_path}}/guides/users/attributes/enable-email-as-username/). Then, the user must enter the email address when logging in.
27
+
{% endif %}
26
28
27
29
!!! tip "Add additional fields to the user onboarding form"
28
30
The default form requests for basic information of the user. If you wish to include additional details, such as the user's phone number, address, and other custom attributes, you need to make these attributes available in the **Administrator Console**. Learn how to do so in [attribute configurations]({{base_path}}/guides/users/attributes/manage-attributes/#configure-attributes).
@@ -248,7 +250,7 @@ During user onboarding, you can enforce email verification to confirm the provid
248
250
"HTTP/1.1 201 Created"
249
251
```
250
252
251
-
5. If you selected the confirmation link option, use can click the link to verify. If you configured OTP, validate it by submitting the OTP using the following API.
253
+
5. If you selected the confirmation link option, users can click the link to verify. If you configured OTP, validate it by submitting the OTP using the following API.
0 commit comments