Page History

...

• By default mutual authentication is in place.
  • JOC Cockpit makes use of two connections to the Controller: one for the JS7 - History Service and one for the JOC Cockpit GUI. Both connections by default use mutual authentication.
  • The JOC Cockpit is challenged by the Controller to present its Client Authentication certificate that is then verified by the Controller.
    • In addition the Distinguished Name of the JOC Cockpit Client Authentication certificate is checked. An additional password setting has to be present but can be empty as in password="plain:". JOC Cockpit ships with the below default passwords. If a password is changed in the Controller configuration then it has to be changed in the JS7 - Settings too.
    • Note that any number of clustered JOC Cockpit instances can connect to a Controller.
  • If a Controller Cluster is used then connections from the partnering Controller instance are authenticated by the Distinguished Name of the instance's Client Authentication certificate.

• The JS7_CONTROLLER_CONFIG_DIR/private/private.conf configuration file should include authentication details such as:

  Code Block
  title Example for private.conf file specifying JOC Cockpit authentication
  js7 { auth { users { # History account (used to release events) History { distinguished-names=[ "DNQ=SOS CA, CN=joc_primary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE" ] password="sha512:B793649879D61613FD3F711B68F7FF3DB19F2FE2D2C136E8523ABC87612219D5AECB4A09035AD88D544E227400A0A56F02BC990CF0D4CB348F8413DE00BCBF08" } # JOC account (needs UpdateItem permission for deployment) JOC { distinguished-names=[ "DNQ=SOS CA, CN=joc_primary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE" ] password="sha512:3662FD6BF84C6B8385FC15F66A137AB75C755147A81CC7AE64092BFE8A18723A7C049D459AB35C059B78FD6028BB61DCFC55801AE3894D2B52401643F17A07FE" permissions=[ UpdateItem ] } # Controller ID for connections by primary/secondary Controller instance jobscheduler { distinguished-names=[ "DNQ=SOS CA, CN=controller_primary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE",                    "DNQ=SOS CA, CN=controller_secondary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE" ] password="plain:"           } }   } }

  
  

  Explanation:
  • The History and JOC user accounts are used by the JS7 - History Service and by the JS7 - REST Web Service API.
    • The distinguished-names property allows the addition of a number of Distinguished Names as available from the subjects of the Client Authentication certificates which are used by JOC Cockpit instances when connecting to the Controller.
      • Except for whitespace between attributes, the precise sequence and values as available from the certificate's subject has to match this property value.
      • If more than one Distinguished Name is used then they are separated by comma.
      • Distinguished Names can be displayed in different flavors. JS7 makes use of RFC2253 compliant Distinguished Names. The following command can be executed to verify the Distinguished Name from a given certificate file:
        • openssl x509 -in <joc-cert.pem> -noout -nameopt RFC2253 -subject
        • The output that you receive - except for a subject: or subject= prefix - should be used as the JOC Cockpit's Distinguished Name
        • Sample Output:
          • subject= ST=Berlin,OU=JS7,O=SOS,L=Berlin,C=DE,CN=centostest-primary
          • The prefix subject= has to be omitted from the Distinguished Name.
    • The password is used for authentication of the History and JOC service accounts with the Controller. Both accounts are typically run in the same JOC Cockpit instance. 
      
      • If HTTP connections are used then the password is the only means for authentication. If HTTPS connections with mutual authentication are used then the password is not relevant as certificate based authentication is in place.
      • The symmetric password is specified in the joc section of the JS7 - Settingspage of the JOC Cockpit and in the private.conf file. 
        • User Input to the Settings page of the JOC Cockpit can look like this:
          
          
          
          Input to the GUI simply accepts the password and does not require the use of the sha512: or plain: prefixes.
      • In the private.conf file a hashed value or a plain text value can be specified like this:
        
        • password="sha512:B793649879D6..."
        • password="plain:JS7-History"
      • If the password is modified in the private.conf file then it has to be modified in the JOC Cockpit settings as well, so that the passwords match.
      • The password setting cannot be omitted. However, an empty password can be specified, for example:
        • password="plain:"
      • From the private.conf file that ships by default the plain text value and the hashed values are:
        • History: 
          • Plain Text: JS7-History
          • Hash: sha512:B793649879D61613FD3F711B68F7FF3DB19F2FE2D2C136E8523ABC87612219D5AECB4A09035AD88D544E227400A0A56F02BC990CF0D4CB348F8413DE00BCBF08
        • JOC:
          • Plain Text: JS7-JOC
          • Hash: sha512:3662FD6BF84C6B8385FC15F66A137AB75C755147A81CC7AE64092BFE8A18723A7C049D459AB35C059B78FD6028BB61DCFC55801AE3894D2B52401643F17A07FE
  • The jobscheduler account is an example of the Controller ID that is used by a partnering Controller instance.
    • This setting is not required if a Standalone Controller is used.
    • For a Controller Cluster the Controller ID is specified during installation.

...