James Mason
Adventist Health
Programmer/Analyst
916.783.2576
[EMAIL PROTECTED]
[EMAIL PROTECTED] 05/26/04 6:11 PM
Yes, JAAS could be used. I didn't think of it before because Slide
seems
to require a little bit more. You need to expose these user nodes and
provide some standard properties. Is
On Tue, 25 May 2004 09:38:25 -0700, James Mason [EMAIL PROTECTED] wrote:
It might be posible to define a standard mechanism, maybe by writing
some Abstract Store class for a partial or transparent store, where
a
store that does not handle an operation it delegates to the parent
store. For example,
Alan Wood wrote:
On Tue, 25 May 2004 09:38:25 -0700, James Mason [EMAIL PROTECTED] wrote:
It might be posible to define a standard mechanism, maybe by writing
some Abstract Store class for a partial or transparent store, where
a
store that does not handle an operation it delegates to the parent
On Thu, 27 May 2004 00:58:07 +0900, Carlos Villegas [EMAIL PROTECTED]
wrote:
Alan Wood wrote:
On Tue, 25 May 2004 09:38:25 -0700, James Mason [EMAIL PROTECTED] wrote:
It might be posible to define a standard mechanism, maybe by writing
some Abstract Store class for a partial or transparent
Alan Wood wrote:
I see where your coming from, using the readonly store implementation
(for say user and password) avoids the transaction issues. But if this
were to be implemented (just user and password) it would be best to
create the store so that it outsourced authentication in a standard
It might be posible to define a standard mechanism, maybe by writing
some Abstract Store class for a partial or transparent store, where
a
store that does not handle an operation it delegates to the parent
store. For example, you mount a standard store on /, Tx or JDBC, and
then you mount
James I think its a great idea, in my opinion would also really help slide
in a number of applications i am working on too.
On Fri, 21 May 2004 11:09:30 -0700, James Mason [EMAIL PROTECTED] wrote:
Here's what I'm hoping to have when I get finished:
1. Tomcat authenticates users against an LDAP
Al,
I'm glad you like the idea :). One of my personal pet peeves is the
lack of LDAP support for user management in a lot of opensource
products, so I'm hoping I can help remedy that a little.
I think one has to consider what the benefits of using LDAP are as a
user
store? I would have thought
I think JNDI may have a benefit here, plus
slide could also benefit from a little JNDI support, again these
are
not
areas of my expertese, just my $0.02, and I would certainly be
prepared to
help as long as the code was contributed back (I.E opensourced).
I'll have to check with my boss
James Mason wrote:
Talking about ACLs gets really sticky. As far as I know every LDAP
server has it's own unique way of managing authorizations internally.
Since LDAP is just a communication protocol I don't think it has any
specifications for this, so I don't know of any standard way to get/set
Here's what I'm hoping to have when I get finished:
1. Tomcat authenticates users against an LDAP repository.
2. Slide authorizes users against an LDAP repository.
3. Slide authorizes groups (or roles) against an LDAP repository.
4. Slide determines group/role membership from user membership in
11 matches
Mail list logo
