> Would you consider committing a change to the interface and
> its various
> implementations to allow for this increased level of security?
The ProfileLocator already has a user object, but it isn't required that its
filled valid.
Sometimes you are working with groups or roles, so when you say a user, do
you mean an admin-type user, or just the current user?
There aren't a lot of methods left after we complete the deprecation:
public PSMLDocument getDocument( ProfileLocator locator );
public boolean saveDocument(PSMLDocument doc);
public PSMLDocument createDocument( ProfileLocator locator );
public Iterator list( ProfileLocator locator );
It would be easy to add a single parameter to all methods - perhaps RunData
would be more useful although it ties the methods to rundata requests.
Do you plan on integrating it with Turbine Security?
There has been a lot of talk on the mailing list, but I don't think the
Turbine folks ever got around to actually implementing a Turbine LDAP
Security Service.
I would think that if you are going to store PSML in LDAP, then you would
want to also store the user info there.
> -----Original Message-----
> From: McClelland, Mark [mailto:Mark.McClelland@divine.com]
> Sent: Monday, August 13, 2001 2:06 PM
> To: jetspeed-dev@jakarta.apache.org
> Subject: Change to PSMLManagerService interface
>
>
> I am working on an LdapPsmlManagerService implementation, and
> I plan to
> modify the PSMLManagerService interface to include either a user or a
> rundata as a parameter in several of the methods, so that LDAP
> credentials can be checked each time PSML is accessed or modified in
> LDAP. I have two questions for the developers:
>
> Would you recommend passing a user or rundata, based on the
> direction of
> Jetspeed?
>
> Would you consider committing a change to the interface and
> its various
> implementations to allow for this increased level of security?
>
> -mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
|