Page History

...

Director Agent Configuration

The following configuration applies to use of a Director Agent in a JS7 - Agent Cluster. 

A single Director Agent and a Director Agent Cluster of two instances can be used.

Client Authentication with Controller

...

• This setting applies to connections to a Subagent of a pairing Director Agent instance in a JS7 - Agent Cluster and to connections to any Subagents.
• Note that the director-primary, director-secondary element names are examples that have to be replaced by the Subagent ID of the pairing Director Agent instance which is specified during configuration of the Agent Cluster. This is not the Agent Cluster ID.
• Note that the subagent-001, subagent-002, ... element names are examples for Subagent IDs of connected Subagents.
• The password element specifies the password indicated with the pairing Director Agent instance's and any Subagent's js7.auth.users.<subagent-id>.password configuration item. Passwords should be quoted. 
  
  • The password must be specified as plain text preceded by plain:. Passwords should be quoted.

Subagent Configuration

xxx

...

• • .

Subagent Configuration

The following configuration applies to use of Subagents in a JS7 - Agent Cluster. 

Client Authentication with Director Agent Instances

Consider that client authentication an alternative to Password Authentication with Director Agent Instances.

Anchor
js7-auth-users-Subagent js7-auth-users-Subagent

Director Agent Connections

js7 {
    auth {
        # User accounts for https connections
        users {
            # Subagent ID of Primary Director Agent instance
            director-primary {
                permissions = [ AgentDirector ]
                distinguished-names=[
                    "DNQ=SOS CA, CN=director-2-0-primary, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE"
                ]
            }

            # Subagent ID of Secondary Director Agent instance
            director-secondary {
                permissions = [ AgentDirector ]
                distinguished-names=[
                    "DNQ=SOS CA, CN=director-2-0-secondary, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE"
                ]
            }
        }
    }
}

Explanation:

• This setting applies to connections from Director Agent instances to the current Subagent in a JS7 - Agent Cluster.
• Note that the director-primary, director-secondary element names are examples that have to be replaced by the Subagent ID of the respective Director Agent instance which is specified during configuration of the Agent Cluster.
• The permissions element should be used as indicated.
• The distinguished-names element identifies the Director Agent instance's Client Authentication certificate. The certificate acts as a replacement for a password.
  
  • Note that the common name (CN) element in the distinguished name has to match the fully qualified domain name (FQDN) of a Director Agent instance's host.

  • The following command can be used to read the distinguished name from a certificate file:
    
    

    Code Block
    title Example for OpenSSL command to read a certificate's distinguished name
    # read distinguished name from the pairing Director Agent instance's certificate openssl x509 -in centostest-secondary.crt -noout -nameopt RFC2253 -subject # output is returned with a prefix "subject= " or similar that is not part of the distinguished name # subject= DNQ=SOS CA,CN=director-2-0-secondary,OU=IT,O=SOS,L=Berlin,ST=Berlin,C=DE

Password Authentication with Director Agent Instances

Consider that password authentication is an alternative to Client Authentication with Director Agent Instances.

Anchor
js7-auth-users-password-Subagent js7-auth-users-password-Subagent

Director Agent Connections

js7 {
    auth {
        # User accounts for https connections
        users {
            # Subagent ID of Primary Director Agent instance
            director-primary {
                permissions = [ AgentDirector ]
                password = "plain:secret-director-primary"
            }

            # Subagent ID of Secondary Director Agent instance
            director-secondary {
                permissions = [ AgentDirector ]
                password = "plain:secret-director-secondary"
             }
         }
    }
}

Explanation:

• This setting applies to the connection from Director Agent instances to the current Subagent in an JS7 - Agent Cluster.
• Note that the director-primary, director-secondary  element names are examples that have to be replaced by the Subagent ID of the respective Director Agent instance which is specified during configuration of the Agent Cluster.
• The permissions element should be used as indicated.
• The password element specifies the password indicated with the respective Director Agent instance's js7.auth.subagents configuration item. Passwords should be quoted.
  • The password can be specified as plain text preceded by plain:.
  • The password can be specified as a hashed value preceded by sha512:.

Server Authentication

Anchor
js7-web-https-keystore js7-web-https-keystore

HTTPS Keystore and Truststore Locations

...