Sorry for not giving any anwser - I actually have the
same question.
I am thinking a third option: let another application
handles authentication and authorization.
my application handles role base access control for
other resources - menu items for example. I am
thinking of extending this to manage the documents as
well.
but I do not know if it is an efficient option or not.
--- Morten <[EMAIL PROTECTED]> wrote:
> Hi.
>
> I will be using Slide as a file system based content
> repository. It will
> be part of a web-application which contains a UI to
> add/remove users and
> set permissions at folder level.
>
> This means I need to integrate Slide with my
> web-app. I see 2 possible
> methods:
>
> 1. Slide accesses an external data-source for
> authentication and
> authorization, possibly via a custom plug-in (could
> be done using WCK,
> but that impacts DeltaV).
>
> 2. The users and permissions get set in Slide
> explicitly using an API
> (pointers to which greatly appreciated).
>
> Functionally, I need to be able to answer the
> questions "Is user X with
> password Y a valid user?" and "Can user X access
> folder Z?"
>
> Which of the above is the preferred approach and
> what is the "proper"
> way to go about it? What's considered best
> practices? Studying WCK,
> Realms, JAAS, Projector gives lots of options on
> authentication, but I
> fail to find options for authorization.
>
> Br,
>
> Morten
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
