Shibboleth Developers

[Dan McLaughlin <>]

You are correct that FqdnSearchResultHandler.java should have nothing
to do with the credential exception. Unless there is an exception
being swallowed somewhere.  My theory until I have a second to step
through it with the debugger is that there is some other exception
that occurs in FqdnSearchResultHandler.java when it is trying to read
the composite name that is eating an exception and things eventually
bubble up as a missing credential exception.

--

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 Wed, Jun 8, 2011 at 11:11 AM, Daniel Fisher 
<>
 wrote:
> On Wed, Jun 8, 2011 at 2:07 AM, Dan McLaughlin
> <>
>  wrote:
>> Hi Daniel,
>>
>> What allowed me to get past the invalid credential error in vt-ldap
>> 3.3.3 was to revert...
>>
>
> This change has nothing to do with the credential (password). If
> you're seeing that error the password is either null or empty.
>
>> "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.
>
> Died how? Was there an exception? Post the trace log and I'll try to
> decipher it.
>
> --Daniel Fisher
>