cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "N. Sean Timm" <>
Subject Re: sitemap draft still needs work in the matcher/chooser area
Date Sun, 18 Jun 2000 18:51:14 GMT
I'm fairly neutral right now on whether or not Cocoon itself does any sort
of authentication or authorization (I haven't spent much time thinking about
it), but I do know that my company has custom authentication methods that
have to occur, and these will be implemented as choosers.  I was just going
to bring up a point about needing a global process path, when I realized
that we have that with the current sitemap proposal.  Now that it's not URI
dependant, I can have my first match be on an authorization chooser, and
then pass them to a login process or on to their requested process depending
on the return!

- Sean T.
----- Original Message -----
From: "brian moseley" <>
To: <>
Sent: Sunday, June 18, 2000 12:32 PM
Subject: Re: sitemap draft still needs work in the matcher/chooser area

> On Sun, 18 Jun 2000, Giacomo Pati wrote:
> > Authentication is the process of identifying who is the
> > requestor. Authorisation is the process of
> > allowing/denying access to the resource requested.
> yes i know that already. your definitions don't prove why
> the mechanical act of authorization should be cocoon's
> responsibility.

View raw message