Shibboleth Developers

[Dan McLaughlin <>]

Hi Daniel,

What allowed me to get past the invalid credential error in vt-ldap
3.3.3 was to revert...

"1877   4/5/11 9:42 AM  4       dfisher SearchResult#getName() returns a 
string
representing a composite name, not necessarily an LDAP DN. Use a
CompositeName to parse it correctly. Add test case for entries with
special characters. Fixes vt-ldap 109."

There was a problem parsing the fqdn url and then things died from
there...  I didn't spend too much time trying to figure out why b/c I
have to get IdP 2.3.0 up and running by the morning.

--

Thanks,

Dan McLaughlin


NOTICE: This e-mail message and all attachments transmitted with it
are for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is strictly prohibited. The contents of
this e-mail are confidential and may be subject to work product
privileges. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.



On Tue, Jun 7, 2011 at 11:27 PM, Daniel Fisher 
<>
 wrote:
> On Tue, Jun 7, 2011 at 8:08 PM, Dan McLaughlin
> <>
>  wrote:
>> Hi Daniel,
>>
>> I don't have a test eDir server on the outside, but I'd be surprised
>> if I couldn't reproduce it with OpenLDAP.
>>
>
> Post an LDIF that's representative of your data.
>
>> By the way... after upgrading to 2.3.0 in our Development environment.
>>  LDAP authentication fails unless I roll back to the vt-ldap jar to
>> the 3.3.2 release.
>>
>> 18:34:46.916 - DEBUG
>> [edu.vt.middleware.ldap.auth.SearchDnResolver:173] - User input was
>> empty or null
>
> The username was either empty or null, and
>
>> 18:34:46.917 - DEBUG [edu.vt.middleware.ldap.jaas.LdapLoginModule:136]
>> - Authentication failed
>> javax.naming.AuthenticationException: Cannot authenticate dn, invalid 
>> credential
>>        at 
>> edu.vt.middleware.ldap.auth.AbstractAuthenticator.authenticateAndAuthorize(AbstractAuthenticator.java:154)
>>
>
> the password was also either empty or null.
>
>> If I roll back only the vt-ldap.jar  to the 3.3.2 release and change
>> nothing else, then the same exact login works fine...
>>
>
> This time the login module received jdoe with a correct password.
>
> --Daniel Fisher
>