...

• The shiro.ini file is not validated by the JOC Cockpit. This means that a configuration error will lead to that entry not being processed.
  
  • For example, a spelling error in a permission will lead to that permission not being set.
  • The permissions granted for an account can be inspected in the JOC Cockpit interface by logging into the interface using that account and checking the Permissions section of the User Profile view

Logging

To get a debug log file for the login procedure please add this to the file $JETTY_BASE/resources/joc/log4j.properties

#logger for security
log4j.logger.com.sos.auth=debug, shiro
log4j.additivity.com.sos.auth= false
log4j.appender.shiro = org.apache.log4j.FileAppender
log4j.appender.shiro.layout = org.apache.log4j.EnhancedPatternLayout
log4j.appender.shiro.layout.ConversionPattern = %d{ISO8601}{Europe/Berlin} %-5p %m%n%throwable{short}
#filename of shiro log
log4j.appender.shiro.File = ${jetty.base}/logs/JOCShiroLog.log

Additional Information

Jetty has to be restarted after changes are made to the [main] section of the shiro.ini file.

...