Differences

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

Link to this comparison view

Both sides previous revision Previous revision
3400_how_to:0800_security_and_protection [2026/08/13 07:33] – Imported by DokuWiki Advanced Plugin aware_support33400_how_to:0800_security_and_protection [2026/08/13 07:43] (current) – Imported by DokuWiki Advanced Plugin aware_support3
Line 5: Line 5:
 <accordion autoclose> <accordion autoclose>
 <anchor id="give_different_authority_to_different_users"> <anchor id="give_different_authority_to_different_users">
-<accordion-item title="give different authority to different users" type="primary">+<accordion-item title="give different authority to different users">
 Most multi-user systems require that different categories of users have access to different features of the system. In //**AwareIM**// this is done by assigning different access levels to different users – see the “[[2000_concepts:0900_prod_feats:0100_access_control:0100_access_level|Access Level]]” section. Most multi-user systems require that different categories of users have access to different features of the system. In //**AwareIM**// this is done by assigning different access levels to different users – see the “[[2000_concepts:0900_prod_feats:0100_access_control:0100_access_level|Access Level]]” section.
 </accordion-item> </accordion-item>
  
 <anchor id="limit_access_to_database_tables"> <anchor id="limit_access_to_database_tables">
-<accordion-item title="limit access to database tables" type="primary">+<accordion-item title="limit access to database tables">
 In //**AwareIM**// you are not dealing with database tables directly – instead you can limit access to business objects – see the “[[2500_config_apps:1400_add_edit_acls|Setting Access to Business Objects]]” section for details. You can also limit access to business objects based on some conditions – see [[:3400_how_to:0800_security_and_protection#define_access_based_on_some_conditions]]. In //**AwareIM**// you are not dealing with database tables directly – instead you can limit access to business objects – see the “[[2500_config_apps:1400_add_edit_acls|Setting Access to Business Objects]]” section for details. You can also limit access to business objects based on some conditions – see [[:3400_how_to:0800_security_and_protection#define_access_based_on_some_conditions]].
 </accordion-item> </accordion-item>
  
 <anchor id="limit_access_to_records"> <anchor id="limit_access_to_records">
-<accordion-item title="limit access to records" type="primary">+<accordion-item title="limit access to records">
 In //**AwareIM**// you are not dealing with database records directly – instead you can limit access to attributes of business objects – see the “[[2500_config_apps:1400_add_edit_acls|Setting Access to Business Objects]]” section for details. You can also limit access to attributes based on some conditions – see [[:3400_how_to:0800_security_and_protection#define_access_based_on_some_conditions]]. In //**AwareIM**// you are not dealing with database records directly – instead you can limit access to attributes of business objects – see the “[[2500_config_apps:1400_add_edit_acls|Setting Access to Business Objects]]” section for details. You can also limit access to attributes based on some conditions – see [[:3400_how_to:0800_security_and_protection#define_access_based_on_some_conditions]].
 </accordion-item> </accordion-item>
  
 <anchor id="limit_access_to_operations"> <anchor id="limit_access_to_operations">
-<accordion-item title="limit access to operations" type="primary">+<accordion-item title="limit access to operations">
 Most operations are invoked from forms - see [[3400_how_to:0200_forms_and_user_interface]]. You can also limit access to processes and services – see the “[[2500_config_apps:1400_add_edit_acls|Adding/Editing Access Levels]]”. Most operations are invoked from forms - see [[3400_how_to:0200_forms_and_user_interface]]. You can also limit access to processes and services – see the “[[2500_config_apps:1400_add_edit_acls|Adding/Editing Access Levels]]”.
  
Line 31: Line 31:
  
 <anchor id="define_access_based_on_some_conditions"> <anchor id="define_access_based_on_some_conditions">
-<accordion-item title="define access based on some conditions" type="primary">+<accordion-item title="define access based on some conditions">
 If you want to limit access to business objects or its attributes based on some conditions you have to specify business rules that use the ''[[ref:a_f:a:protect|PROTECT]]'' action. See the description of the ''[[ref:a_f:a:protect|PROTECT]]'' action in the [[:3000_rule_language|Rule Language Reference]] for details. If you want to limit access to business objects or its attributes based on some conditions you have to specify business rules that use the ''[[ref:a_f:a:protect|PROTECT]]'' action. See the description of the ''[[ref:a_f:a:protect|PROTECT]]'' action in the [[:3000_rule_language|Rule Language Reference]] for details.
 </accordion-item> </accordion-item>
  
 <anchor id="get_end_users_to_define_their_own_access_restrictions"> <anchor id="get_end_users_to_define_their_own_access_restrictions">
-<accordion-item title="get end users to define their own access restrictions" type="primary">+<accordion-item title="get end users to define their own access restrictions">
 Sometimes it may be necessary for end users (for example, system administrators) to override access restrictions supplied by developers. This could be the case if developers sell their application to many different customers each of them having their own unique access level requirements.  Sometimes it may be necessary for end users (for example, system administrators) to override access restrictions supplied by developers. This could be the case if developers sell their application to many different customers each of them having their own unique access level requirements. 
  
Line 43: Line 43:
  
 <anchor id="implement_multi_tenancy"> <anchor id="implement_multi_tenancy">
-<accordion-item title="implement multi-tenancy" type="primary">+<accordion-item title="implement multi-tenancy">
 It is often required that the same application is hosted for different “tenants”. A tenant logs into the system and only sees data that belongs to him, but not other tenants. It is often required that the same application is hosted for different “tenants”. A tenant logs into the system and only sees data that belongs to him, but not other tenants.
  
Line 70: Line 70:
  
 <anchor id="set_up_ssl"> <anchor id="set_up_ssl">
-<accordion-item title="set up SSL" type="primary">+<accordion-item title="set up SSL">
 //**AwareIM**// uses web server such as Tomcat or Weblogic to process web requests. The default web server that comes with //**AwareIM**// is Tomcat. If you want //**AwareIM**// to use SSL protocol for the web requests you can set up the web server to use SSL. Please refer to the documentation of the web server. See also the [[:1100_inst_guide|AwareIM Installation Guide]]. //**AwareIM**// uses web server such as Tomcat or Weblogic to process web requests. The default web server that comes with //**AwareIM**// is Tomcat. If you want //**AwareIM**// to use SSL protocol for the web requests you can set up the web server to use SSL. Please refer to the documentation of the web server. See also the [[:1100_inst_guide|AwareIM Installation Guide]].
 </accordion-item> </accordion-item>
  
 </accordion> </accordion>