Page History

...

• This allows to operate JS7 products in different network zones. JOC Cockpit can be located in a deployment zone from which users deploy workflows. Controllers and Agents can be operated in separate more secure network zones.
• The underlying principle is to allow connections from a less secure deployment zone to more secure zones and to deny connections to go the opposite way.
• If jobs are operated on JS7 Agents that require access to the JS7 REST Web Service API then it is recommended to set up additional JOC Cockpit API Server instances. Such instances do not include the user interface but serve the REST Web Service API only. Any number of API Server instances can be set up & operated in parallel and they can be operated located close to JS7 Agents.

Network Connections

...

• Using the default root user account that ships with the JOC Cockpit is not recommended. The default user account is intended to enable initial login only.
• A fine-grained set of permissions is available that can be applied to any operation in the JOC Cockpit and in the JS7 REST Web Service API. Such permissions can freely be grouped to roles, see JS7 - Authorization.
• JS7 - Identity Services offer a number of authentication methods that can be combined for single-factor and multi-factor authentication (MFA).
  
  • The JS7 - LDAP Identity Service can be used to establish role assignment for users based on membership in LDAP Directory Service security groups.
  • The JS7 - Certificate Identity Service and JS7 - FIDO2 FIDO Identity Service can be used for MFA.

Identity Services

...

• Users can switch to one of the supported Identity Services such as
  • JS7 - LDAP Identity Service,
    • LDAP Directory Services can be accessed for authentication and authorization:
      • users can connect by specifying their domain account.
      • membership in security groups can be optionally mapped to roles managed with JOC Cockpit.
    • The use of LDAP allows operation of a JOC Cockpit configuration that contains neither user account data, passwords nor user role assignments. 
    • This applies to any LDAP compliant product such as Microsoft Active Directory®, OpenLDAP etc.
  • JS7 - OIDC Identity Service
    • OIDC offers token based authentication that includes a direct connection between the user and the Identity Provider.
    • JOC Cockpit has no access to passwords in this authentication scheme.
  • JS7 - Certificate Identity Service
    • Client Authentication certificates can act as a replacement for passwords.
    • The Identity Service can be used for single-factor authentication and for MFA.
  • JS7 - FIDO2 FIDO Identity Service
    • Public/private key authentication by use of a secure device eliminates the use of passwords.
    • The Identity Service can be used for single-factor authentication and for MFA.
• A number of Identity Services can be combined to be optional or required. This allows to authenticate with one Identity Service from a list of available services and it allows to force authentication with all configured Identity Services.
• Users should consider to disable the initial JOC Identity Service when more secure Identity Services are in place.

...