With JobScheduler release 1.7. JID will have a login option.
If you are updating from an older version, the following changes will be made to your configuration
- JID will be connected to a JobScheduler instance identified by an scheduler id. The scheduler id will be part of the call parameters in dashboard.sh|cmd
- In the file $scheduler_data/config/scheduler.xml of the JobSchedulerInstance with which JID will be connected, two new parameters are included.
<param name="security_server_address" value="http://localhost:nnnnn"/>
<param name="security_server_enabled" value="true"/>
- security_server_address is the host:port address of the security server. Normally it is the JobScheduler connectet to JID.
- With security_server_enabled you can disable the login and JID will start without login. The permissions will be set by the call parameters -enable_joe -enable_events -enable_joc
- In the table scheduler_instances a new field named jetty_port number (9) is added. It must contain the jetty_port of the security server.
- In the classpath configured in the file factory.ini will be enhanced by the config directory of the security server
- In the config directory of the security server a file shiro.ini will be saved. Also an example for authentification with LDAP or with a database. The file shiro.ini defines a user root/root that will have all permissions.
- In the file scheduler.xml of the security server a plugin will be added
<plugin java_class="com.sos.jobscheduler.tools.webservices.SOSCommandSecurityPlugin">
<plugin.config/>
</plugin>
and in the fileweb.xml
<servlet>
<servlet-name>Jersey REST Service</servlet-name>
<servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class>
<init-param>
<param-name>com.sun.jersey.config.property.packages</param-name>
<param-value>com.sos.auth.rest</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Jersey REST Service</servlet-name>
<url-pattern>/rest/*</url-pattern>
</servlet-mapping>