Introduction

• The JS7 - Identity Services offer local management of user accounts for authentication and authorization.
• The Shiro Identity Service was a built-in service available with the JOC Cockpit
  • The Shiro Identity Service was available for early releases of JS7.
  • The Shiro Identity Service has been discontinued: 
    FEATURE AVAILABILITY ENDING WITH RELEASE 2.4.0
• A migration tool is available for users who are upgrading from early JS7 2.0, 2.1 releases or who are migrating from JS1 1.12, 1.13 releases.
  • For details see JS7 - Shiro Identity Service Migration
  • The JS7 - Shiro Identity Service Migration Tool will remain in place and can be applied throughout future JS7 2.x releases independently of the fact that the Shiro Identity Service has been discontinued.

Identity Service Type

The following integration level is available from Identity Service Types that can be used with JOC:

Explanation:

• Service Type: SHIRO
  • Management of user accounts and passwords is performed by the JOC Cockpit.
  • The assignment of roles to user accounts is performed by the JOC Cockpit.
  • The JOC Cockpit stores user accounts, hashed passwords and role assignments:
    • in the JS7 - Database and
    • in the JETTY_BASE/resources/joc/shiro.ini.active file.
    • Users can create a copy of the shiro.ini.active file, add their modifications and submit changes by renaming the file to shiro.ini. With the next login of a user the shiro.ini file will be applied and its contents added to the JS7 database. As a result of this operation the shiro.ini file is renamed to shiro.ini.active. A previously available shiro.ini.active file will be renamed to shiro.ini.backup.

Identity Service Configuration

The JOC Cockpit provides the Manage Identity Services page for the configuration of Identity Services. This page is accessed from the user menu of an administrative account::

Identity Service Settings

No settings are required for use of the Shiro Identity Service.

Logging

• Log Files
  • See JS7 - Log Files and Locations
• Standard Log Files
  • Identity Services log output to the JETTY_BASE/logs/joc.log file. This includes reporting success or failure of authentication.
  • Successful and failed authentication attempts including user accounts involved are logged to the JETTY_BASE/logs/audit.log file.
• Debug Log Files
  • For problem analysis during setup of an Identity Service increase the log level as explained with JS7 - Log Levels and Debug Options.
  • The JETTY_BASE/logs/joc-debug.log file includes general debug output of JOC Cockpit.
  • The JETTY_BASE/logs/authentication-debug.log file includes debug output related to authentication and authorization.
  • The JETTY_BASE/logs/jetty.log file includes debug output of attempts to establish SSL connections.