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

[xenophon\+shibboleth]

Peter Schober writes:
> 
> I'd start by looking at the Shibboleth IdP's log files, not the
> container's.

Scott Cantor writes:
> 
> The error is what you posted it is. Your LDAP connection isn't
working,
> and the IdP won't start up if the connected systems aren't alive.

Thank you both.  This helped.

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:

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, but I just found
the ResolverLDAPDataConnector wiki page
(https://wiki.shibboleth.net/confluence/display/SHIB2/ResolverLDAPDataCo
nnector) and am reading through it now.  If possible I'd like to
temporarily disable the SSL/TLS connection requirement, as enabling
LDAPS on our domain controllers is out of the scope of the current
project.

Best wishes,
Matthew

-- 
I FIGHT FOR THE USERS