RE: Linux account integration

2004-04-30 Thread Alex Karasulu
> -Original Message- > From: Steve Brewin [mailto:[EMAIL PROTECTED] > Sent: Friday, April 30, 2004 3:54 PM > To: 'James Developers List' > Subject: RE: Linux account integration > > Serge Knystautas wrote: > > I'll give it a whirl soon... looks like JDK 1.4 comes bundled > > with the > >

RE: Linux account integration

2004-04-30 Thread Alex Karasulu
Serge, > > I'm pretty confident this is the case. Perhaps someone else can > > confirm as well. > > Reading the docs for the NIS service provider, one of the docs says it > requires, "A server that speaks the YP Version 2 protocol, such as the > Solaris/NIS server, and the Solaris/NIS+ server run

RE: Linux account integration

2004-04-30 Thread Steve Brewin
Serge Knystautas wrote: > I'll give it a whirl soon... looks like JDK 1.4 comes bundled > with the > NIS impl, so James would need to include those service providers > separately. Pretty sure I'm being a pedant here and you really meant this, but "include those service providers"? Install as requi

Re: Linux account integration

2004-04-30 Thread Serge Knystautas
Alex Karasulu wrote: Actually I think the NIS provider talks to the underlying NSS libraries which abstract away the exact mechanism. So underneath the hood the OS can be configured to be using LDAP or NIS or even NIS+ for the NSS and the API would remain the same - the user wouldn't have to w

Re: Linux account integration

2004-04-30 Thread Serge Knystautas
Alex Karasulu wrote: Actually I think the NIS provider talks to the underlying NSS libraries which abstract away the exact mechanism. So underneath the hood the OS can be configured to be using LDAP or NIS or even NIS+ for the NSS and the API would remain the same - the user wouldn't have to w

RE: Linux account integration

2004-04-30 Thread Noel J. Bergman
Serge Knystautas wrote: > Noel J. Bergman wrote: > > FWIW, there is a read-only NIS provider for JNDI. I don't know > > of a similar one for the Windows login system, but the NIS one > > can be used to access local login information on linux. > Wouldn't this require someone running an NIS daemon?

RE: Linux account integration

2004-04-30 Thread Alex Karasulu
Serge, > -Original Message- > From: Serge Knystautas [mailto:[EMAIL PROTECTED] > Sent: Friday, April 30, 2004 2:35 PM > To: James Developers List > Cc: Alex Karasulu > Subject: Re: Linux account integration > > Noel J. Bergman wrote: > > FWIW, there is a read-only NIS provider for JNDI.

Re: Linux account integration

2004-04-30 Thread Serge Knystautas
Noel J. Bergman wrote: FWIW, there is a read-only NIS provider for JNDI. I don't know of a similar one for the Windows login system, but the NIS one can be used to access local login information on linux. I just downloaded it to take a look (http://java.sun.com/products/jndi/serviceproviders.html

RE: Linux account integration

2004-04-30 Thread Alex Karasulu
> -Original Message- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Friday, April 30, 2004 2:03 PM > To: James Developers List > Cc: Alex Karasulu > Subject: RE: Linux account integration > > FWIW: > http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/spec/com/sun/secur > i

RE: Linux account integration

2004-04-30 Thread Noel J. Bergman
FWIW: http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/spec/com/sun/securit y/auth/module/package-summary.html JAAS can access anything that is supported by JNDI, plus NT, NIS (as well as NIS through JNDI), etc. --- Noel ---

RE: Linux account integration

2004-04-30 Thread Noel J. Bergman
Serge, > I'm thinking of creating another user implementation that extends the > current file one, but when it does the authentication, it will check > against the Linux account. > This is so I don't have to setup an LDAP server but otherwise can let > people use their same passwords. FWIW, ther

[jira] Commented: (JAMES-275) src distrinution doesnt build, missing phoenix stuff.

2004-04-30 Thread jira
The following comment has been added to this issue: Author: Noel J. Bergman Created: Fri, 30 Apr 2004 8:52 AM Body: There are two source distributions. One without: http://cvs.apache.org/builds/james-server/test-build/src/james-2.2.0RC2-src.zip and one with Phoenix: http://cvs.

Re: [CANDIDATES] avalon release candidates - round 1

2004-04-30 Thread mcconnell
This message sent to you via a very slightly modified version of James HEAD running all of the release candidates listed below. Cheers, Steve. Stephen McConnell wrote: The following Avalon release candidates have been posted to http://www.apache.org/~mcconnell/candidates * avalon-framework (ap

[CANDIDATES] avalon release candidates - round 1

2004-04-30 Thread Stephen McConnell
The following Avalon release candidates have been posted to http://www.apache.org/~mcconnell/candidates * avalon-framework (api/impl)4.2 * avalon-logging 2.0 * excalibur-lifecycle (api/impl) 1.2 * excalibur-pool (api/impl) 2.0 * excalibur-thread (api/impl)2.0

Re: Linux account integration

2004-04-30 Thread Serge Knystautas
Intelekia wrote: Hi Serge, The best option is JAAS (Java Authentication and Authorization Service), introduced as an optional package in J2SE 1.3 and integrated into J2SE 1.4. It implements a Java Pluggable Authentication Module (PAM) framework to provide single authentication against Unix, Window

[jira] Created: (JAMES-275) src distrinution doesnt build, missing phoenix stuff.

2004-04-30 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://issues.apache.org/jira/browse/JAMES-275 Here is an overview of the issue: -

RE: Linux account integration

2004-04-30 Thread Intelekia
Hi Serge, The best option is JAAS (Java Authentication and Authorization Service), introduced as an optional package in J2SE 1.3 and integrated into J2SE 1.4. It implements a Java Pluggable Authentication Module (PAM) framework to provide single authentication against Unix, Windows, Kerberos, etc.