McClelland, Mark wrote:
A profile locator param in the saveDocument method would solve a
significant part of my problem. Would you be interested in diff -u
patches for this?
That would be great.
The rest of my problem probably has more to do with the Turbine security
service than
the
LDAP issues aside for now.
-mark
-Original Message-
From: Raphaël Luta [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 12:34 PM
To: [EMAIL PROTECTED]
Subject: Re: Change to PSMLManagerService interface
McClelland, Mark wrote:
There aren't a lot of methods left after we
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
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
It is my understanding that the user on the ProfileLocator is
the owner
of the PSML document -- not necessarily the user currently
logged in.
true
want an admin user to be able to log in and make a change that affects
other users. In a corporate setting, this sort of change is
McClelland, Mark wrote:
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
McClelland, Mark wrote:
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
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
