JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

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

Identity Service Type

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

Identity ServiceIdentity Service Configuration ItemsJOC Cockpit Configuration
Service TypeBuilt-inUser Accounts/Passwords
stored with		User Accounts/Passwords
managed by		Roles/Permissions
stored with		Roles->User Accounts Mapping
managed with		Announcement
SHIROyesJS7 Database / shiro.iniJOC CockpitJS7 Database / shiro.iniJOC Cockpit

The SHIRO Service Type is

  • deprecated with release 2.2.0
  • unsupported with release 2.3.0
  • removed with release 2.4.0


Explanation:

  • Service Type: SHIRO
    • Management of user accounts and passwords is performed with JOC Cockpit.
    • The assignment of roles to user accounts is performed with JOC Cockpit.
    • JOC Cockpit stores user accounts, hashed passwords and role assignments
      • in the JS7 - Database and
      • to the JETTY_BASE/resources/joc/shiro.ini.active file (for information purposes)
      • 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 are 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 is renamed to shiro.ini.backup.

Identity Service Configuration

JOC Cockpit offers the Manage Identity Services page from the user menu of an administrative account for configuration of Identity Services:

Identity Service Settings

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

Logging

  • Log Files
  • Standard Log Files
    • Identity Services log output to the JETTY_BASE/logs/joc.log file. This includes to report 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.


  • No labels