Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

Tectia

Configuration Task Flow

Tectia configurations are handled differently from other configurations in Tectia Manager. A Tectia configuration can stay in edit state between administration interface sessions and changes to the configuration do not take effect until the configuration is commited.

It is also possible to view previously commited revisions of Tectia configurations, and to compare previously commited configurations to each other or to the configuration under editing. See Viewing and Comparing Configurations.

The names of Tectia configurations under editing are shown in green and the settings can be changed on the configuration subpages. The names of Tectia configurations that have been commited are shown in black, and the settings can be only viewed on the configuration subpages.

Tectia configurations have the following structure:

  • The Tectia Client configuration is used by Tectia Client and Tectia ConnectSecure. Each client configuration can contain several connection profiles that specify settings for connecting to different Secure Shell servers.

  • The Tectia Server configuration is used by Tectia Server. Each server configuration can contain several service rules that are applied to users based on matching selectors.

Tectia Client and Server configurations

Figure 11.1. Tectia Client and Server configurations

Tectia Client

The task flow for Tectia Client configuration settings is illustrated in Figure 11.2.

Defining Tectia Client configurations

Figure 11.2. Defining Tectia Client configurations

  1. Create a new configuration object or open an existing configuration for editing. Define the general, PKI, logging, connection, and transparent tunneling settings.

  2. Optionally, create connection profiles that define special settings for each Secure Shell server the client is connecting to. The profile names must be unique.

  3. Commit the changes to the configuration.

Assign and deploy the configuration set as described in Assigning Configurations per Group and Deploying Configurations.

[Note]Note

Only a configuration that has been commited can be deployed to a Tectia Client/ConnectSecure host. Clicking Save is required after changing check boxes or text fields in the configuration pages, but the saved settings are not immediately deployable.

Example of the PKI settings in the Tectia Client configuration

Figure 11.3. Example of the PKI settings in the Tectia Client configuration

Configuring Tectia Server

The server configuration task flow is illustrated in Figure 11.4.

Defining Tectia Server configurations

Figure 11.4. Defining Tectia Server configurations

  1. Create a new configuration object or open an existing configuration for editing. Define the general, PKI, logging, and connection settings.

  2. Create one or more rules and define the selectors for each rule. Selectors define the user group that will use that particular rule. Define the authentication, basic services, SFTP, and tunneling settings for the rule.

  3. Commit the changes to the configuration.

Assign and deploy the configuration set as described in Assigning Configurations per Group and Deploying Configurations.

[Note]Note

Only a configuration that has been commited can be deployed to a Tectia Server host. Clicking Save is required after changing check boxes or text fields in the configuration pages, but the saved settings are not immediately deployable.

Tectia Server G3 configuration

Figure 11.5. Tectia Server G3 configuration

===AUTO_SCHEMA_MARKUP===