LDAP (AD) Authentication Service

2003-07-22 Thread jetspeed-dev
The following is an LDAP (AD) Authentication Service that does not require modifying the structure of Active Directory. It was written to be configured as a turbine service and configurable via the attached JetspeedSecurity.properties modifications and additions. The plan is to add any

LDAP/AD Authentication Service

2003-08-14 Thread jetspeed-dev
Below is modification to an LDAP Authentication service I previously submitted to this mailing list to authenticate users of LDAP/AD. Add parameters section of text to you Jetspeed's JetspeedSecurity.properties file and configure to use the class below. Drop the jar of the class into /webapps

RE: LDAP (AD) Authentication Service

2003-07-23 Thread Aurelien Pernoud
[EMAIL PROTECTED] a écrit : > > Note: The first time a user authenticates, their Jetspeed database > entry is created, but for some reason the user will have to > re-authenticate again to > completely log in for the first time. Later authentications do not > need this additional step. I'm unsure

RE: LDAP/AD Authentication Service

2003-08-14 Thread Mark Orciuch
> Sent: Thursday, August 14, 2003 12:39 PM > To: [EMAIL PROTECTED] > Subject: LDAP/AD Authentication Service > > > > Below is modification to an LDAP Authentication service I > previously submitted > to this mailing list to authenticate users of LDAP/AD. > > Add param

Re: Re: LDAP (AD) Authentication Service

2003-07-23 Thread jetspeed-dev
"Aurelien Pernoud" <[EMAIL PROTECTED]> writes: > I've found a similar case here, cause in my app I'm creating users > PSML when users first login (looks like what you're doing too), I'm > using another app to populate users (login/pwd...). Is the error > something related with a null profile or

RE: Re: LDAP (AD) Authentication Service

2003-07-23 Thread Aurelien Pernoud
[EMAIL PROTECTED] a écrit : > I get a bit more content, but that's about it. I've fiddled with it > from several different angles and I can't get past this issue. I > suppose, I might have to trace deeper into supporting frameworks... > We've applied a business rule for now to cover the issue.