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
Disabling a user's account prevents users from logging into applications or to the self-service My Account portal. It is intended to be a long-term and a more permanent measure than locking a user's account. Therefore, if you simply wish to restrict a user's access temporarily, it is recommended to use [account locking](#lock-a-user-account).
313
317
314
318
!!! note "Enable account disabling"
315
-
319
+
316
320
Account disabling is not an option available for a user's account by default. If you wish to enable this option for your organization, refer to [account disabling]({{base_path}}/guides/account-configurations/account-disabling/).
- A username is always unique to the organization and you can't change the username once it is created.
27
-
- Instead of using a username to login, you can [configure email address as the username]({{base_path}}/guides/users/attributes/enable-email-as-username/). Then, you will be asked to enter the email address when logging in.
28
-
- The user can change the password set by the administrator from the [My Account Portal]({{base_path}}/guides/user-self-service/customer-self-service-portal/).
26
+
- The user's username is always unique to the organization and you can't change the username once it is created.
27
+
- 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.
28
+
29
+
!!! tip "Add additional fields to the user onboarding form"
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).
29
31
30
32
3. You can either request the user to set the password or set one on the user's behalf.
Alternatively, administrators can use the resend-code API to resend the link or code as shown below.
153
+
Alternatively, administrators can use the resend-code API to resend the link or code as shown below.
152
154
153
155
!!! abstract ""
154
156
@@ -194,7 +196,7 @@ Alternatively, administrators can use the resend-code API to resend the link or
194
196
]
195
197
}'
196
198
```
197
-
199
+
198
200
The recovery scenario should be specified in the properties parameter of the API request body, as follows:
199
201
200
202
- `ASK_PASSWORD`: When the user is pending to set up an initial password using the setup link.
@@ -242,7 +244,7 @@ To reset the password:
242
244
If this option is selected, the owner or an administrator can set a new password for the user.
243
245
244
246
!!! note
245
-
If the user is in pending admin forced password reset, once the admin resets the password,
247
+
If the user is in pending admin forced password reset, once the admin resets the password,
246
248
the account will get unlocked.
247
249
248
250
- **Invite user to reset the password:**
@@ -311,7 +313,7 @@ To lock a user account:
311
313
Disabling a user's account prevents users from logging into applications or to the self-service My Account portal. It is intended to be a long-term and a more permanent measure than locking a user's account. Therefore, if you simply wish to restrict a user's access temporarily, it is recommended to use [account locking](#lock-a-user-account).
312
314
313
315
!!! note "Enable account disabling"
314
-
316
+
315
317
Account disabling is not an option available for a users' accounts by default. If you wish to enable this option for your organization, refer to [account disabling]({{base_path}}/guides/account-configurations/account-disabling/).
Copy file name to clipboardExpand all lines: en/includes/guides/users/attributes/manage-attributes.md
+8-2
Original file line number
Diff line number
Diff line change
@@ -136,6 +136,12 @@ To configure properties of user attributes:
136
136
</tbody>
137
137
</table>
138
138
139
+
!!! note
140
+
Using the attribute configurations, you can also configure which attributes are displayed in the user creation form when
141
+
[onboarding users]({{base_path}}/guides/users/manage-users/#onboard-a-single-user) in the console.
142
+
143
+
To display an attribute in the user creation form, select the **both** **Display** and **Required** checkboxes for the **Administrator Console** entity.
144
+
139
145
{% else %}
140
146
141
147
## Configure attributes
@@ -200,7 +206,7 @@ To configure properties of user attributes:
200
206
!!! warning "Before you proceed"
201
207
202
208
Attributes cannot be deleted if it has any associations with external schema. If you have attribute mappings, make sure you delete these associations before attempting to delete an attribute.
203
-
209
+
204
210
Refer to [Delete an OpenID Connect attribute]({{base_path}}/guides/users/attributes/manage-oidc-attribute-mappings/#delete-an-openid-connect-attribute) and [Delete a SCIM2 attribute]({{base_path}}/guides/users/attributes/manage-scim2-attribute-mappings/#delete-a-scim-20-custom-schema-attribute) to delete any existing associations.
205
211
206
212
@@ -236,7 +242,7 @@ datastore_type = "<Name of the identityDataStore class>"
236
242
237
243
By making this configuration adjustment, you can ensure that your system aligns with your preferred data store class, whether it's the previous default or a custom class you've implemented. This helps you tailor the system to your specific needs.
238
244
239
-
2. Map the identity claims mentioned below to attributes in the underlying user store.
245
+
2. Map the identity claims mentioned below to attributes in the underlying user store.
240
246
241
247
!!! info
242
248
Learn more about [adding claim mapping]({{base_path}}/guides/dialects/add-claim-mapping).
0 commit comments