Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Subject: Re: Dynamic or Static Access Control Lists
From: Thorsten Scherler <thorsten@apache.org>
To: forrest dev <dev@forrest.apache.org>
In-Reply-To: <002e01c4cfa2$0ee97910$0200a8c0@vaio>
References: <002e01c4cfa2$0ee97910$0200a8c0@vaio>
Content-Type: text/plain; charset=iso-8859-1
Message-Id: <1101041777.3443.42.camel@gci>
Mime-Version: 1.0
Date: Sun, 21 Nov 2004 13:56:17 +0100
Content-Transfer-Encoding: 8bit

El dom, 21-11-2004 a las 09:13, Alex Batlin escribi�:
> Has anyone configured Forrest to allow user to provide userid and
> password, and then generated documents based on their role/group.
> Document elements can then be tagged with role/group. I am thinking of
> the way profiling is done in DocCook.

No, not AFAIK, but it should be quite easy.

I will need auth as well pretty soon for profiling. You can either beat
me by sending a patch or hang in there and wait (I guess end of the
year) till I implemend it.

Basicly you have to do the following for auth, protected docs and
profiling:
1) create a dir where the protected docs go
2) create a auth pipeline where you start the session
3) add profiling to the session in your profiling
4) change your skin pipelines to display the profiled content

Can you open an enhancement issue and add this to it. This way it will
not get lost.
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)