Reviewing references to user attribute management and UIs
Closes #26155 Signed-off-by: Pedro Igor <pigor.craveiro@gmail.com>
Before Width: | Height: | Size: 82 KiB After Width: | Height: | Size: 67 KiB |
Before Width: | Height: | Size: 94 KiB After Width: | Height: | Size: 24 KiB |
Before Width: | Height: | Size: 174 KiB After Width: | Height: | Size: 25 KiB |
Before Width: | Height: | Size: 132 KiB After Width: | Height: | Size: 32 KiB |
Before Width: | Height: | Size: 76 KiB After Width: | Height: | Size: 34 KiB |
After Width: | Height: | Size: 50 KiB |
Before Width: | Height: | Size: 140 KiB After Width: | Height: | Size: 49 KiB |
Before Width: | Height: | Size: 75 KiB After Width: | Height: | Size: 37 KiB |
|
@ -173,7 +173,7 @@ users you'll see that each user detail page is read only, except for the `Role M
|
|||
Going to this tab you'll find that there are no `Available` roles for the admin to
|
||||
map to the user except when we browse the `sales-application` roles.
|
||||
|
||||
.Add viewleads
|
||||
.Assign viewLeads
|
||||
image:images/fine-grain-add-view-leads.png[Fine grain add view leads]
|
||||
|
||||
We've only specified that the `sales-admin` can map the `viewLeads` role.
|
||||
|
|
|
@ -5,12 +5,12 @@
|
|||
From the Admin Console, you have a wide range of actions you can perform to manage users.
|
||||
|
||||
include::users/proc-creating-user.adoc[leveloffset=+2]
|
||||
include::users/user-profile.adoc[leveloffset=+2]
|
||||
|
||||
include::users/ref-user-credentials.adoc[leveloffset=+2]
|
||||
include::users/proc-setting-password-user.adoc[leveloffset=+3]
|
||||
include::users/proc-creating-otp.adoc[leveloffset=+3]
|
||||
|
||||
include::users/proc-configuring-user-attributes.adoc[leveloffset=+2]
|
||||
include::users/con-user-registration.adoc[leveloffset=+2]
|
||||
include::users/proc-enabling-user-registration.adoc[leveloffset=3]
|
||||
include::users/proc-registering-new-user.adoc[leveloffset=3]
|
||||
|
@ -31,6 +31,5 @@ include::users/proc-allow-user-to-delete-account.adoc[leveloffset=+2]
|
|||
include::users/con-user-impersonation.adoc[leveloffset=+2]
|
||||
include::users/proc-enabling-recaptcha.adoc[leveloffset=+2]
|
||||
|
||||
include::users/user-profile.adoc[leveloffset=+2]
|
||||
include::users/ref-personal-data-collected.adoc[leveloffset=+2]
|
||||
|
||||
|
|
|
@ -26,7 +26,7 @@ The Execution requirements section includes an example of the OTP form.
|
|||
`Condition - User Attribute`::
|
||||
This checks if the user has set up the required attribute: optionally, the check can also evaluate the group attributes.
|
||||
There is a possibility to negate output, which means the user should not have the attribute.
|
||||
The xref:proc-configuring-user-attributes_{context}[User Attributes] section shows how to add a custom attribute.
|
||||
The link:#user-profile[User Attributes] section shows how to add a custom attribute.
|
||||
You can provide these fields:
|
||||
|
||||
Alias:::
|
||||
|
|
|
@ -14,7 +14,7 @@ Any user with the `impersonation` role in the realm can impersonate a user.
|
|||
. Click a user to impersonate.
|
||||
. From the *Actions* list, select *Impersonate*.
|
||||
+
|
||||
image:images/user-details.png[]
|
||||
image:images/user-impersonate-action.png[]
|
||||
|
||||
* If the administrator and the user are in the same realm, then the administrator will be logged out and automatically logged in as the user being impersonated.
|
||||
* If the administrator and user are in different realms, the administrator will remain logged in, and additionally will be logged in as the user in that user's realm.
|
||||
|
|
|
@ -1,27 +0,0 @@
|
|||
// Module included in the following assemblies:
|
||||
//
|
||||
// server_admin/topics/users.adoc
|
||||
|
||||
[id="proc-configuring-user-attributes_{context}"]
|
||||
= Configuring user attributes
|
||||
|
||||
User attributes provide a customized experience for each user. You can create a personalized identity for each user in the console by configuring user attributes.
|
||||
|
||||
.Users
|
||||
image:images/user-attributes.png[]
|
||||
|
||||
.Prerequisite
|
||||
* You are in the realm where the user exists.
|
||||
|
||||
.Procedure
|
||||
. Click *Users* in the menu.
|
||||
. Select a user to manage.
|
||||
. Click the *Attributes* tab.
|
||||
. Enter the attribute name in the *Key* field.
|
||||
. Enter the attribute value in the *Value* field.
|
||||
. Click *Save*.
|
||||
|
||||
|
||||
NOTE: Some read-only attributes are not supposed to be updated by the administrators. This includes attributes that are read-only
|
||||
by design like for example `LDAP_ID`, which is filled automatically by the LDAP provider. Some other attributes should be read-only for
|
||||
typical user administrators due to security reasons. See the details in the xref:read_only_user_attributes[Mitigating security threats] chapter.
|
|
@ -1,5 +1,5 @@
|
|||
[[user-profile]]
|
||||
= Defining a user profile
|
||||
= Managing user attributes
|
||||
|
||||
In {project_name} a user is associated with a set of attributes. These attributes are used to better describe and identify
|
||||
users within {project_name} as well as to pass over additional information about them to applications.
|
||||
|
|