A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1318.html

Document ID: 1318
Branch: main
Language: default
Name: Protection (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 12/8/07 9:18:37 AM
Updated by: Job Honig

A new version has been created, state: draft

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 4851 bytes (previous version: 4806 bytes)
Content diff:
(2 equal lines skipped)
    
    <h2>Protecting Documents</h2>
    
--- <p>One feature of Cocoon Auth is user authentication and protecting 
documents. A
+++ <p>One feature of Cocoon Auth is user authentication and document 
protection. A
    document can be accessible for everyone, it can be accessible by 
authenticated
--- users or the user needs more credentials than just being logged in to read 
it -
--- for example she has to be in a specific role.</p>
+++ users only, or it can be accessible to users who supply additional 
credentials
+++ (apart from just being logged in) to read it - for example she has to be in 
a
+++ specific role.</p>
    
    <p>There are several ways of protecting a document:</p>
    
(2 equal lines skipped)
    an authenticated users.</li>
    <li>The Sitemap: Cocoon Auth provides some actions to protect pipelines. The
    checks range from testing if the user is authenticated, over if the user 
has a
--- role to more specific, custom access checks.</li>
+++ role, to more specific, custom access checks.</li>
    <li>Cocoon Flow: Cocoon Auth provides some FlowScript functions that make 
the
    same checks that are possible in a sitemap available to the flow controller.
    </li>
(9 equal lines skipped)
    <li>Cocoon Auth checks (using one of the methods mentioned above) if this
    document is protected. If no protection is specified, the response is this
    original document.</li>
--- <li>If the document is protected, Cocoon Auth checks, if the user is
+++ <li>If the document is protected, Cocoon Auth checks if the user is
    authenticated.</li>
    <li>If the user is authenticated, the response is the original document. If 
the
    user is not authenticated, the application logic has to deal with this. For
(88 equal lines skipped)