Page History

...

 <plugins>
   <plugin java_class="com.sos.scheduler.engine.plugins.jetty.JettyPlugin">
     <plugin.config>
       <loginService>
         <logins>
           <login name="testName" password="testPassword" roles="administratorSecurityLevel.all"/>
         </logins>
       </loginService>
     </logins>
       </loginService>
/plugin.config>
   </plugin>
 </plugins>

SecurityLevel.info and SecurityLevel.all are predefined roles for JobScheduler.

SecurityLevel.info allows only rights for watching but not for starting jobs, while SecurityLevel.all allows additionally the right for starting jobs.

Add a security constraint to the web.xml:

    <security-constraint>
        <web-resource-collection>
            <url-pattern>/*</url-pattern>
        </web-resource-collection>
        <auth-constraint>
            <role-name>SecurityLevel.info</role-name>
            <role-name>SecurityLevel.all</role-name>
        </plugin.config>auth-constraint>
   </plugin>
 </plugins>security-constraint>

</span>

<span id"jetty">

Configure jetty.xml

...

The properties file config/realm.properties contains one or more user definitions, e.g.

   testuser: test, admin
   infouser: test, SecurityLevel.info
   alluser: test, SecurityLevel.all

Please note: In realm.properties you can specify the password like

  testuseralluser: MD5:098f6bcd4621d373cade4e832627b4f6, adminSecurityLevel.all

Hint: You can use the MD5 Key generated by JOE but you have to change it to lowercase.

...

    <security-constraint>
        <web-resource-collection>
            <url-pattern>/*</url-pattern>
        </web-resource-collection>
        <auth-constraint>
            <role-name>admin</role-name>
            <role-name>SecurityLevel.info</role-name>
            <role-name>SecurityLevel.all</role-name>
        </auth-constraint>
    </security-constraint>

...