Job Scheduler itself can only do simple name/password authentication. The easiest way to generate the encryted passwords is to use the Job Editor.
If you want to authenticate against ldap, you can set up a web server (e.g. apache) as a proxy for the Job Scheduler Operations Gui (4444). Then allow only localhost and the web server to contact Job Scheduler (see <allowed_hosts> in scheduler.xml).
Now, if someone wants to access the Operations Gui, he needs to use the address of the proxy. This proxy address can the be secured using plugins of the web server (e.g. Apache's ldap plugin).
Configuring a Proxy
Load the proxy module in httpd.conf:
LoadModule proxy_module modules/mod_proxy.so
Configure a proxy address
<Proxy http://scheduler_host:4444/*> Order deny,allow Allow from all </Proxy> ProxyPass /scheduler/ http://scheduler_host:4444/ ProxyPassReverse /scheduler/ http://scheduler_host:4444/
After restarting apache, Job Scheduler should be accessable by opening http://proxy_host/scheduler.
Configuring ldap authentication
First, make sure the proxy for Job Scheduler is working. Then the proxy can be secured using apache's ldap plugin.
Load ldap modules:
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so LoadModule ldap_module modules/mod_ldap.so
Secure the proxy:
<Proxy http://scheduler_host:4444/*> AuthzLDAPAuthoritative off AuthBasicProvider ldap AuthType Basic AuthName "LDAP Job Scheduler" AuthLDAPURL ldap://your_host/ou=People,dc=my-domain,dc=com require valid-user AuthBasicProvider ldap AuthzLDAPAuthoritative off </Proxy>