Login issue

[Peter Schober]

* Gilles Badouet <badouetg at uni.coventry.ac.uk> [2013-07-03 17:42]:
> I am using 8443 for IdP https access because the standard 443 is
> already used in IIS for my SP.

You could have both on port 443 by tunnelling to Tomcat from MS-IIS:
http://tomcat.apache.org/connectors-doc/webserver_howto/iis.html
Jfyi.

> Concerning the current issue, I added <logger
> name="edu.vt.middleware.ldap.jaas.JaasAuthenticator" level="DEBUG"
> /> in my logging.xml file but still cant see any change in IdP
> side. In LDAP logs, I cant neither see any issue related to IdP.

How are you authenticating users in your IdP?
Do you use the default edu.vt.middleware.ldap.jaas.LdapLoginModule in
login.config? (If you post your config make sure to remove any
passwords prior to sending). If so the line I sent you should have
lots of information on the LDAP connection, try searching your
idp-process.log for lines with "fgrep edu.vt.middleware.ldap.jaas".

On your LDAP DSA side, "not seeing an issue" does not say much. So you
can verify that the connection from the IDP has been established
correctly, that a bind with the DN (it's not, but your DSA seems to
want this broken syntax) "Administrator at ADdomain" succeeds? That
subsequent LDAP search operations return non-null number of objects?
That all returned result codes are successful?

You should probably verify the connection parameters required for your
LDAP DSA works with some other tool. (Personally I'd use OpenLDAP's
ldapsearch but there are plenty of others, e.g. Apache Directory
Studio, LDAPExplorerTool, IXplorer, etc.). If you have something
"known good" migrate those settings to your IdP.
-peter