new:user_and_security
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
new:user_and_security [2016/09/16 04:37] ca |
new:user_and_security [2016/09/20 03:03] (current) ca |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | **User's & Security** | + | =====Users & Security===== |
| * a very fine-grained level of detail in assigning permissions. | * a very fine-grained level of detail in assigning permissions. | ||
| * User-level security allows the database administrator to group users with similar needs into common pools. Permission can then be granted to work group instead of to individual users, easing the administration of permissions. | * User-level security allows the database administrator to group users with similar needs into common pools. Permission can then be granted to work group instead of to individual users, easing the administration of permissions. | ||
| - | {{ :cecille:u_s-account_creation.png |}}{{ :new:u_s-list_of_users.png |}} | ||
| - | *** The importance of User's, Roles and Permissions** | ||
| - | - **Users** are the **people** | ||
| - | - **roles** are their **functions**,and | ||
| - | - **permissions** define what **authorizations** those functions have. | ||
| - | **Roles** | ||
| - | * This is a principle by which developers create a systems that limit access or restrict operations according to a user's constructed role within a system. This is also often called **role-based** principle to ensure that authorized users do not gain access to privileged information. | ||
| - | * {{ :new:u_s-role.png |}} | ||
| - | **Team**. | + | |
| + | |||
| + | The best practices for securing your system users, roles,& permissions are based on the following ideas: | ||
| + | - Rethink your roles | ||
| + | - Know the defaults | ||
| + | - Evaluate your elevated permissions | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | The importance of User's, Roles and Permissions | ||
| + | * **Users** are the **people** | ||
| + | * **Roles** are their **Functions**,and | ||
| + | * **Permissions** define what **Authorizations** those functions have. | ||
| + | |||
| + | //<wrap em>Sample page for creating user account</wrap>//{{ :cecille:u_s-account_creation.png |}} | ||
| + | |||
| + | |||
| + | //<wrap em>Sample page for the list of system Users</wrap>//{{ :new:u_s-list_of_users.png |}} | ||
| + | |||
| + | =====Roles===== | ||
| + | * This is a principle by which developers create a systems that limit access or restrict operations according to a user's defined role within a system. This is also often called **role-based** principle to ensure that authorized users do not gain access to privileged information. | ||
| + | //<wrap em>Sample page for Roles definition</wrap>//{{ :new:u_s-role.png |}} | ||
| + | |||
| + | =====Teams===== | ||
| * After you have defined the Team, you can link the Team member to the Team and Role. By doing so, you can access to any of the transaction entry by **Team**. | * After you have defined the Team, you can link the Team member to the Team and Role. By doing so, you can access to any of the transaction entry by **Team**. | ||
| - | * {{ :new:u_s-teams.png |}} | + | //<wrap em>Sample page for creating by Teams</wrap>//{{ :new:u_s-teams.png |}} |
| - | **Limit** | + | =====Limits===== |
| * The function on user Limit is activated for a particular transaction type only if you have set any limit for at least one user for one transaction type. | * The function on user Limit is activated for a particular transaction type only if you have set any limit for at least one user for one transaction type. | ||
| - | * {{ :new:u_s-limits.png |}} | + | //<wrap em>Sample page for activating Limits</wrap>//{{ :new:u_s-limits.png |}} |
| | | ||
| - | **Visibility** | + | =====Visibility===== |
| * Once you set up any value for a particular context, all users not satisfying the condition will be barred from viewing any record in all lists in the system. | * Once you set up any value for a particular context, all users not satisfying the condition will be barred from viewing any record in all lists in the system. | ||
| - | * {{ :new:u_s-visibility.png |}} | + | //<wrap em>Sample page for setting visibility</wrap>// {{ :new:u_s-visibility.png |}} |
| - | <wrap em>**The best practices for securing your system users, roles,& permissions are based on the following ideas:**</wrap> | ||
| - | - Rethink your roles | ||
| - | - Know the defaults | ||
| - | - Evaluate your elevated permissions | ||
/srv/www/htdocs/wiki/data/attic/new/user_and_security.1474000641.txt.gz · Last modified: 2016/09/16 04:37 by ca
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
