Page History
...
Introduction
The architecture introduced with the of JOC Cockpit ensures that users are restricted to directly accessing the JOC Cockpit as illustrated in the diagram below. The JOC Cockpit calls the JS7 - REST Web Service API which, in turn, has access to the JS7 Controller instances. There is no connection from the JOC Cockpit to Agents.
...
| Situation | Remember Me | Remember Me |
|---|---|---|
| User logs out, browser reverts to Log In page | Authorization token is invalidated by the logout | Authorization token is deleted with the session storage |
| Session expires, browser reverts to Log In page | Authorization token is deleted | Authorization token is deleted with the session storage |
| New browser tab is opened in parallel to an existing browser tab | Authorization token in existing tab is valid Authorization token is required for new tab | Authorization token is maintained with the session storage |
| Browser tab is closed during session and then reopened by opening the recent tab | Authorization token is invalidated | Authorization token is deleted with the session storage |
Browser tab is closed during session and then reopened by opening login page | Authorization token is invalidated | Authorization token is deleted with the session storage |
Note that:
- the browserThe browser's local storage will not be emptied after a period of time when Remember Me is set and a user does not log in again.
...
The JOC Cockpit uses the idle timeout period set in the shiro.ini configuration file for user sessions:
| Code Block | ||||
|---|---|---|---|---|
| ||||
securityManager.sessionManager.globalSessionTimeout = 900000 |
for user sessions which is available from the Manage Global Settings button in the Identity Services page :
The default value is The default value of 900.000 milliseconds translates to 15 minutes. The JOC Cockpit has to be restarted to does not require a restart to apply changes made to this value.
...
The JOC Cockpit ships with a default setting in the shiro.ini configuration file for the account "root" with the password "root" and setting for the default user account that is configured with the JOC-INITIAL Identity Service. By default the root user account and password root is used with permissions to carry out all operations with the JOC Cockpit.
Adjust Users should adjust the account and password to be used. For secure configuration it is recommended that LDAP access to a Directory Service is configured for users user accounts with roles managed in the shiro.ini file and by an JS7 - LDAP Identity Service and that the "root" account is dropped. This guarantees that general policies such as password rotation or password complexity requirements are considered when using the JOC Cockpit.
See the Authentication and Authorization - Configuration article for more information.
Default Profile Account
JOC Cockpit stores the userusers' s profile settings in its database. When a user logs in for the first time then the settings of the default profile account are copied to the user profile. By default the profile of the "root" user account that ships with the shiro.ini file JOC-INITIAL Identity Service is used as the default user profile.
The default profile account can be specified with the following setting in the JETTY_BASE/resources/joc/joc.properties file:
| Code Block | ||||
|---|---|---|---|---|
| ||||
################################################################################
### A default profile should be available that includes any profile settings
### that are applied by default to new users.
default_profile_account = root |
default_profile_account setting in section "joc" of the JS7 - Settings page.
Audit Log
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
Security for Users
Use of the Log In Form Remember Me Checkbox
...
- The Log In form will not be emptied after a period of time when Remember Me is set and a user does not log in again,
- The behavior specified in the table above is independent of whether or not the browser is configured to store login information.
Use of the Remember Me functionality can be disabled by applying the following setting to the JETTY_BASE/resources/joc/joc.properties file:
...
| title | Disable Remember Me setting in joc.properties file |
|---|
...
modifying the enable_remember_me setting in the "joc" section of the JS7 - Settings page.
Password Reset and Password Change
A user account's password cannot can be reset or changed with the JOC Cockpit . Depending on the configuration set in the shiro.ini configuration file:if a JS7 - JOC Identity Service is used.
- When resetting or modifying a user account's password then the user is forced to specify a new password with the next login.
- This functionality by design is not offered for an JS7 - LDAP Identity Service or other external Identity Service
- users should ask their system administrator to modify their password in the
shiro.inifile if local user management is used, - any password changes effected for a directory service are automatically considered when using the JOC Cockpit if LDAP configuration is used.
Further Resources
...
Overview
Content Tools