Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Last revision Both sides next revision
devel:documentation:role_attributes [2019/01/18 10:22]
tomiskar 		devel:documentation:role_attributes [2019/04/11 13:36]
kopro information about confidential attributes
Line 2: Line 2:
  
 ====== Attributes of role ====== ====== Attributes of role ======
-{{tag>role attributes}} +{{tag>role attributes parameters assigned parametrization}}
-===== What are an attributes of role? ===== +
-**Role attributes define** what additional information **can (must)** be filled in the user's **assigned role**. A typical example can be the **IP address** of a user's end station, which must be filled in in a role assignment request.+
  
-**Definitions of which attributes** are to be filled for the role are managed on the **role detail** (role attributes tab). Here, you define not only what attributes to show in the request, but also their **default values** and **validation settings**. This definition is part of the **role approval** (off by default).+===== What are role attributes ===== 
 +**Role attributes determine** what additional information **can (must)** be filled in a user's **assigned role**. A typical example can be the **IP address** of a user's end station, which must be filled in a role assignment request.
  
 +The **definitions of what attributes** are to be filled for the role are managed on the **role detail** (role attributes tab). Here, you define not only what attributes to show in the request, but also their **default values** and **validation settings**. This definition is part of the **role approval** process (off by default).
 +
 +
 +===== How it works =====
  
-===== How it works? ===== 
 ==== Definition ==== ==== Definition ====
-First, you need to **create main definition** of all attributes witch could be used in role **sub-definition**. **Main form definition** can be created in **Form definitions** agenda. +First, you need to **create the main definition** of all attributes which could be used in role **sub-definition**. The **main form definition** can be created in the **Form definitions** agenda. 
-<note>Attribute from the **main definition** can be used multiple times in multiple roles.</note>+<note>Attributes from the **main definition** can be used multiple times in multiple roles.</note>
 <note tip>**Main definition** must be created for type **IdmIdentityRole**.</note> <note tip>**Main definition** must be created for type **IdmIdentityRole**.</note>
 +<note important>**Now isn't supported confidential attributes!**</note>
  
 Then, you need to **create sub-definition** of attributes witch should be filled in requesting a role.  Then, you need to **create sub-definition** of attributes witch should be filled in requesting a role. 
Line 85: Line 88:
 Role: [RoleWithTwoAttributes] Attributes: [[Number of fingers:[20], IP:[168.192.0.10]]] Role: [RoleWithTwoAttributes] Attributes: [[Number of fingers:[20], IP:[168.192.0.10]]]
 </code> </code>
 +
 +
 +===== Admin guide (to be completed)=====
 +  * [[.attributes:adm:attributes|Role attributes]]
  • by svandav