Hello Antonio, you have somewhere a database, ldap directory or (for tests)
an xml file storing ID, password, permissions for each user, and then the
authentication simply happens the way you prefer, with an action etc.
All the pages are protected by the same handler.
Have a nice day,
Babs
Hi Antonio,
an interesting scenario - are you serious? :-)
The authentication framework allows you to pass additional data back from
the authentication pipeline. One solution would be to use the same handler
for all the different pipelines but to pass back additional values that
contain the
Hi Barbara I see you posting always! ;) Thanks,
So Do you mean the best approach is to put the permission to every file
into the data element of the auth-protect action? Then check this
permission into each page?
The auth-session data will return something like:
authentication
thing or another.
Interesting thread anyway :-)
Barbara
- Original Message -
From: Antonio Gallardo Rivera [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 05, 2002 9:08 AM
Subject: Re: [Auth-framwork] - How to manage multiple documents.
Hi Barbara I see you posting
I've done mine as Carsten proposed, by using the parameters returned by
the AuthAction in the pipeline. Works great for protecting multiple pages!
But if you want to show different things for different users, you will
have to use the SessionTransformer.
It can be done inside a xsp-page too, but
