Difference between revisions of "Permission system - Users, Groups, Roles"

From ActionApps Documentation
Jump to: navigation, search
 
Line 1: Line 1:
 
== Protecting slice data against an unathorized read access ==
 
== Protecting slice data against an unathorized read access ==
<aafaq id=1667> ~ToDo: 1667 Protecting sensitive data against reading </aafaq>
+
<div class="aafaq" id="faq1667"><aafaq id=1667> ~ToDo: id=1667 Protecting sensitive data against reading rel:1702,</aafaq>
 +
==== FAQ: Protecting sensitive data against reading ====
 +
 
 +
<br />With the concept of Reader management slices introduced it is important that
 +
some data are not accessible for reading. This is achieved by setting a reading
 +
password for slices containing sensitive data. If you fill the field "Reading
 +
Password" in Slice Settings, you must always sent this password as a
 +
parameter <code>slice_pwd</code>. This may be done by adding this parameter
 +
to SSI includes like
 +
<br /><code><!--#include virtual="/aa/slice.php3?slice_pwd=the_password&slice_id=xy...."--></code>
 +
<br />If somebody tries to fetch read-protected data without the correct password, all fields are filled with an error message.
 +
<br />If you are interested, the password is prooved in the GetItemContent() function. For AA control panel pages (Item Manager and Item Edit), the function FetchSliceReadingPassword() is used.
 +
 
 +
 
 +
 
 +
</div>

Revision as of 00:01, 25 August 2005

Protecting slice data against an unathorized read access

Protecting sensitive data against reading

With the concept of Reader management slices introduced it is important that some data are not accessible for reading. This is achieved by setting a reading password for slices containing sensitive data. If you fill the field "Reading Password" in Slice Settings, you must always sent this password as a parameter slice_pwd. This may be done by adding this parameter to SSI includes like

<!--#include virtual="/aa/slice.php3?slice_pwd=the_password&slice_id=xy...."-->

If somebody tries to fetch read-protected data without the correct password, all fields are filled with an error message.

If you are interested, the password is prooved in the GetItemContent() function. For AA control panel pages (Item Manager and Item Edit), the function FetchSliceReadingPassword() is used.


FAQ: Protecting sensitive data against reading


With the concept of Reader management slices introduced it is important that some data are not accessible for reading. This is achieved by setting a reading password for slices containing sensitive data. If you fill the field "Reading Password" in Slice Settings, you must always sent this password as a parameter slice_pwd. This may be done by adding this parameter to SSI includes like

If somebody tries to fetch read-protected data without the correct password, all fields are filled with an error message.
If you are interested, the password is prooved in the GetItemContent() function. For AA control panel pages (Item Manager and Item Edit), the function FetchSliceReadingPassword() is used.