Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • JS7 - Identity Services implement Authentication Methods and access to Identity Providers. For example, for example credentials such as user account/password are used as an Authentication Method to access an LDAP Directory Service acting as the Identity Provider, see see the JS7 - Identity and Access Management article for more information.
  • Depending on the Identity Service Type in use, the user accounts are managed and stored with the Identity Service or with the JOC Cockpit, see JS7 - Identity Services.
  • The JOC Cockpit manages permissions and roles for any Identity Services and stores such information independently from of the Identity Service.
  • Find details from the following articles:

...

  • The JOC Identity Service is active and is the only Identity Service available by default.
  • The JOC Identity Service includes the default root user account. Users are encouraged to change the password of the root user account after initial installation of the JOC Cockpit.

To manage user accounts, roles and permissions from any JOC Cockpit page, use the user menu in the right upper corner and select Manage Identity Services:

...

  • Roles: Permissions can freely be grouped to roles. This includes to specify specifying permissions for scheduling objects in the JOC Cockpit and in Controllers.
  • Accounts: Management of user accounts that are stored with the JS7 - Database.
  • Profiles: Information about the date of last login by user accounts.

The Roles sub-view

The Roles sub-view allows to assign assignment of permissions for access to scheduling objects with the JOC Cockpit and Controllers.

When the sub-view is opened after initial installation of JOC Cockpit, then it is populated from with default roles and permissions, see see the JS7 - Default Roles and Permissions article for more information. Users are free to modify, to add and to delete any roles. Please keep in mind that at least one role that includes administrative permissions to access all objects in the JOC Cockpit and Controllers is required and has to be assigned an administrative user account. Should no an administrative role no longer be left then this corresponds to locking the door behind you and throwing away the keys. In this situation consider refer to the JS7 - Rescue in case of lost access to JOC Cockpit article.


The Accounts sub-view

The Accounts sub-view is available when a user selects the Identity Service from the Identity Management Services page. The  This sub-view lists the user accounts that are configured along with their roles.

...

This view allows graphical navigation and the selection of permissions:



...