IdP status page returns "HTTP Status 404" using the quickinstaller on Windows Server 2008 R2

[Peter Schober]

* xenophon\+shibboleth <xenophon+shibboleth at irtnog.org> [2012-10-25 13:49]:
> After I posted to the list, I ran a packet capture while starting up
> Tomcat, and indeed, the IdP fails to bind to LDAP.  Specifically, it
> attempts an SSL/TLS connection (Wireshark reports it as a
> LDAP_START_TLS_OID), which we don't currently support on our domain
> controllers (they respond with LDAP error DSID-0C090E17).  I confirmed
> this by finding the following error in the idp-process log file:

The first thing you'd usually do is check the logs of the application
that failed. Sometimes (severe errors preventing the contect from
starting) there's not even a log entry written by the application
(might happen with JAAS problems), then checking the container's logs
would be necessary.

> 05:42:04.970 - ERROR
> [edu.vt.middleware.ldap.pool.DefaultLdapFactory:109] - unabled to
> connect to the ldap
> javax.naming.ServiceUnavailableException: [LDAP: error code 52 -
> 00000000: LdapErr: DSID-0C090E17, comment: Error initializing SSL/TLS,
> data 0, v1db1 ]
> 
> I didn't realize LDAPS was a connection requirement

It isn't. There must have been useStartTLS="true" in the data
connector (the other way would be specifying ldaps as a protocol but
then LDAP_START_TLS_OID wouldn't show up in the packet trace).
-peter