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
FEATURE AVAILABILITY ENDING WITH RELEASE 2.4.0

Identity Service Type

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

Identity Service				Identity Service Configuration Items		JOC Cockpit Configuration
Service Type	Built-in	User Accounts/Passwords stored with	User Accounts/Passwords managed by	Roles/Permissions stored with	Roles->User Accounts Mapping managed with	Roles Mapping
Shiro	yes	shiro.ini	JOC Cockpit	shiro.ini	shiro.ini	n/a

Explanation:

Service Type: JOC
- 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.

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

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

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 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.