The usage for ED-Lite and ED-Auth does not require client certificate authentication, however using ED-ID does.
To do this you must configure an edldap.properties file.
The edldap.properties file must reside in your classpath (ex: WEB-INF/classes for most web applications), alternatively you may specify the location of the edldap.properties file by setting a Java System Property called “edldap.properties” with its value as the absolute path to the file (ex: java -Dedldap.properties=”/path/to/edldap.properties”).
An edldap.property configuration directive consists of the following format:
edldap.<directory_type>.ssl.<property>=<value>
<directory_type> can be one of **edid**, **edlite**, or **edauth**.
EDLdap Library supports both JKS, BKS …
… and X509 formats for client authentication.
To use ED-ID with a PEM formatted certificate and key the following configuration may be used:
Setting the .trustCertificatesPath and .truststorePath should be optional as the default certificate chain is included with the library.
Command Line Usage
The library also supports command-line interface to perform all of its features which may be used in cron jobs or scripting.
eldap commandline usage:
The following uses ED-Auth to authenticate and authorize the PID ‘ememisya’ using the existence of the affiliation VT-FACULTY as its authorization requirement.
The output is as follows:
All failures in EdAuth will throw edu.vt.middleware.ldap.ed.EdAuthAuthorizationException