6.3.6 Information set in definitions of Connection Destinations

This section describes the definition information you set when adding or editing a Connection Destination in the JP1/AO interface or by using a command.

Broadly speaking, there are two categories of information that make up the definition of a Connection Destination:

Destination information

Information that permits a service to connect to a Connection Destination. You must set destination information if you want a service in any service group other than DefaultServiceGroup to be able to connect to a particular device.
Authentication information

Information used to undergo authentication with the Connection Destination. You do not need to specify authentication information in the definition of the Connection Destination if the user will enter it when submitting the service.

The following table lists the information in the definition of a Connection Destination:

Table 6‒3: Information in Connection Destination definition
Category	Item	Description
Destination information	Method	Select the format in which the Connection Destination is specified, as one of the following: Host Name^#1 IPv4 IPv6
	Destination	Specify the destination or destinations in the appropriate format. You can specify a maximum of 1,024 characters. You can use the following methods: Single destination Range of destinations All destinations
	Service Group	Specify the name of the service group with which to associate the Connection Destination. Services in the specified service group can only access the Connection Destinations specified by the destination information. If you specify DefaultServiceGroup, all services in DefaultServiceGroup will have access to all Connection Destinations.
Authentication information^#2	Protocol	Select one of the following authentication protocols to use for communication with the destination host: SSH Windows Telnet
	SSH Authentication Method	If you select SSH as the protocol, specify the authentication method to use for communication with the destination host. Specify one of the following: Password Authentication Public Key Authentication Keyboard Interactive Authentication
	User ID	Specify the user ID of a user account that can remotely log in to the destination host. When specifying a domain user, use one of the following formats: `domain-name`\`user-name` `user-name`@`domain-name`
	Password	Specify the password corresponding to the user ID. You must specify a password if either of the following applies: Windows is selected as the protocol Password Authentication or Keyboard Interactive Authentication is selected as the SSH authentication method
	Superuser Password^#3	If you selected SSH or Telnet as the protocol, specify the password of the superuser on the destination host. Whether you need to specify the superuser password depends on the definition of the service template. For example, you must specify a superuser password if the service template definition requires root privileges for the command line or file transfer operations. Check the specifications of the service template and plug-ins used by the service.

#1: If the host name resolves to more than one IP address, JP1/AO allocates all of the IP addresses to the destination.
#2: Specify only one set of authentication information for each destination. If you specify more than one set of authentication information for the same destination, authentication might fail.

When executing a General command plug-in, file-transfer plug-in, or content plug-in, a service uses SSH to connect to target devices that run UNIX. When using SSH, JP1/AO logs in as the user specified as the User ID in the authentication information. If the service is configured to elevate the user to a root user after login, you must specify the superuser password in the authentication information. How you specify whether to elevate the user depends on the plug-in, as follows:
- For General command plug-ins and file-transfer plug-ins
  
  Specify true (elevate to root user) or false (do not elevate to root user) in the elevatePrivileges plug-in property.
- For content plug-ins
  
  To elevate to root user, select the Enabled check box for Execute with root privileges (SSH) in the Create Custom Plug-in or Edit Custom Plug-in dialog box. If you do not want to elevate the user, leave the check box cleared.
In a terminal command plug-in, if you specify the reserved property reserved.terminal.suPassword as the value of the commandLine plug-in property, you must specify the superuser password.
For a General command plug-in, file-transfer plug-in, or content plug-in, if you want to use SSH as the protocol when connecting to the destination, the shell specified as the default on the connection destination host must meet the condition below. The condition depends on whether the user will be elevated to a root user. Specify the shell as follows:
- When elevating the user to root user
  
  The default shell for the connecting user and the root user must be sh, bash, ksh, csh, or tcsh.
- When not elevating the user to root user
  
  The default shell for the connecting user must be sh, bash, ksh, csh, or tcsh.