...

• Identity Services implement Authentication Methods and access to Identity Providers, for . For example, credentials such as user account/password are can be used as an Authentication Method to access an LDAP Directory Service acting as the Identity Provider, see . See JS7 - Identity and Access Management.
• JOC Cockpit implements a flexible architecture that allows to add external Identity Service products to be added with future JS7 releases.
• By default JS7 ships with two built-in Identity Services:
  • The JS7 - JOC Identity Service includes to manage which includes management of user accounts with the JOC Cockpit and to use uses the JS7 database for persistence.
  • The JS7 - LDAP Identity Service includes to authenticate authentication of users with an LDAP Directory Service.

  • Display feature availability
    StartingFromRelease 2.2.0

• For compatibility reasons, early releases of JS7 include the JS7 - Shiro Identity Service, see 

  Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1145

  • Display feature availability
    EndingWithRelease 2.3.0

...

Identity Services can be used in a number of flavors depending on the fact :

• which application manages user accounts/passwords:
  • the Identity Provider that is specific to an Identity Service,
  • JOC Cockpit that propagates user accounts/passwords to the Identity Service but does not store such credentials with the JS7 database.
• where assignments of roles to user accounts are stored:
  • with the Identity Provider of the Identity Service,
  • with the JS7 database.
    
    

Management of Identity Services

The operation to manage Management of Identity Services is available accessed from the user menu of an administrative user account in the right upper corner of any JOC Cockpit page:

...

• By default a number of built-in Identity Services are available:
  • JS7 - JOC Identity Service
  • JS7 - LDAP Identity Service
• In addition, connectors are available for external Identity Service products:
  • JS7 - HashiCorp® Vault Identity Service
• The following Identity Services are considered to be deprecated and are removed from future JS7 releases:
  • The JS7 - Shiro Identity Service
    

    Display feature availability
    EndingWithRelease 2.4.0

    
    
    

...

Addition of an Identity Service

To add an Identity Service use the button Add Identity Service from the above list of Identity Services shown above:

The remaining input fields for the popup window look like this:

...

• The Identity Service Name can be freely chosen.
• The Identity Service Type can be selected as available from the matrix shown above matrix.
• The Ordering specifies the sequence in which a login is performed with the available Identity Services.
• The Required attribute specifies if login with the respective an Identity Service is required to be successful, for example, if a number of Identity Services are triggered on login of with a user account.
• The Identity Service Authentication Scheme allows to selectselection of:
  
  • single-factor authentication : - a single factor is sufficient for login with the Identity Service that . This can be configured to make use of:
    • an optional user account and password 
    • an optional Client Authentication Certificate,  see JS7 - Certificate based Authentication
  • two-factor authentication: authentication - two factors are required for login with the Identity Service using:
    • a user account and password and
    • a Client Authentication Certificate.

...

Settings are available at a global level and per individual Identity Service levels.

Anchor
global_settings global_settings

Global Settings

...

• Session Idle Timeout (Default: 900 seconds)
  • If users are inactive for the given number of seconds then the user session expires and is terminated. Users can specify credentials and login to create a new user session.
  • Should the lifetime of an access token provided by an external Identity Service be different from the maximum idle-timeout, then the JOC Cockpit will try to renew the access token with the Identity Service. Renewal of an access token does not require the user to repeatedly re-specify their login credentials for login.
  • Identity Services can restrict the lifetime of access tokens (time to live) and they can limit renewal of access tokens (maximum time to live). If an access token cannot be renewed then the user session is terminated and the user is required to perform a login.
• Initial Password (Default: initial)
  • If an administrator adds user accounts with the JOC Cockpit and does not specify a password then the Initial Password will be used. As a general rule the JOC Cockpit does not allow to the use of empty passwords but populates them from the Initial Password if no a password is not specified by the user that adds adding or modifies modifying an account.
  • In addition, the operation to reset a user account's password is available that . This replaces an existing password with the Initial Password.
  • If the Initial Password is assigned, then a flag is set with for the user account to change indicate that the password has to be changed with the next login. This behavior ensures that users cannot use the Initial Password except for initial login.
• Minimum Password Length (Default 0)
  • For any passwords specified - including the Initial Password - a minimum length is specified.
  • Consider Note that the number of characters and arbitrariness of character selection are key factors for secure passwords. Password complexity requiring e.g. digits and special characters to be used do not substantially add to password security except in case of short passwords.

Settings specific

...

to Individual Identity Services

Such These settings are explained with the individual for each Identity Service individually:

• JS7 - JOC Identity Service (does not require any settings)
• JS7 - LDAP Identity Service
• JS7 - HashiCorp® Vault Identity Service.
• JS7 - Shiro Identity Service (does not require any settings)

...

• Required Identity Services: user login is performed with all required Identity Services.
  • No Optional Identity Services are considered.
  • If more than one Required Identity Service is configured then a user cannot log in if the login fails with any of the Required Identity Services.
  • Permissions are applied from roles assigned by the Identity Services that is the last one last Identity Service in the sequence of enabled Identity Services required to authenticate a user account.
• Optional Identity Services: with the first successful login to an Identity Service the user is considered being logged in.
  • No further optional Identity Services are consulted if a user login is successful with one of the Optional Identity Services.
  • For example, if two Optional Identity Services JOC and LDAP are configured in this sequence then the login to the JOC Identity Service can fail and still the user might successfully login with the LDAP Identity Service.
  • Permissions from the successful login to an Optional Identity Service are used.
• Disabled Identity Services are not considered for user login.

...

Consider that a number of Identity Providers, for example LDAP being used for Active Directory access, might not accept repeatedly repeat failed login attempts and might block the respective relevant user account.

Further Resources

...