Changes between Version 27 and Version 28 of S3/S3AAA/OrgAuth

Timestamp:

09/04/12 10:21:05 (12 years ago)

Author:

Dominic König

Comment:

--

S3/S3AAA/OrgAuth

@@ -23 +23 @@
 [[Image(orgauth1.png)]]
 
-The realm for each role assignment can be chosen from the "''for Entity''" list.
+To remove role assignments, tick the respective checkboxes under "Currently Assigned Roles" and then click "Remove.
+
+To assign another role, choose the role from the drop-down list under "Assign Another Role", choose the realm for the assignment from the ''"For Entity"'' drop-down and then click "Add".
+
+The realm for each role assignment can be chosen from the ''"For Entity"'' list.
 
 [[Image(orgauth2.png)]]
 
-In this list there is also an entry for "All Entities" which means that this role assignment is ''not'' restricted to a realm, but applies site-side (=for all records regardless of their respective owner entity).
+In this list there is also an entry for '''All Entities''' which means that this role assignment is ''not'' restricted to a realm, but applies ''site-wide'' (=for all records regardless of their respective owner entity).
 
-The entry "Default Realm" means all entities the user is (or will be) an organisation unit of at the time of the request authorization.
+The entry '''Default Realm''' means all entities the user is (or will be) an organisation unit of at the time of the request authorization.
 
   '''NOTE:''' The "Default Realm" setting can be dangerous and may be inappropriate for most multi-tenancy settings, because the user would automatically receive this role for any entity they will ever join in future - without that entity being anyhow in control of this. However, in certain deployments, this dynamic realm may still be convenient practice.