| C H A P T E R 2 |
This chapter describes how to configure the SGD Gateway for typical deployment scenarios. How to start and stop the SGD Gateway is also covered in this chapter, along with instructions on how to remove the SGD Gateway software.
This section describes the following SGD Gateway deployment scenarios:
This section describes the configuration tasks for a basic deployment of the SGD Gateway.
A basic deployment uses a single SGD Gateway, as shown in FIGURE 2-1.

Configuring a basic deployment involves configuring the connections shown in TABLE 2-1.
| Connection | Configuration Steps |
|---|---|
| Client device to SGD Gateway |
|
| SGD Gateway to SGD servers |
|
This section describes the configuration tasks for a load-balanced deployment of SGD Gateway.
A load-balanced deployment uses multiple SGD Gateways and a load balancer as the network entry point, as shown in FIGURE 2-2.

Configuring a load-balanced deployment involves configuring the connections shown in TABLE 2-1.
| Connection | Configuration tasks |
|---|---|
| Client device to load balancer |
|
| Load balancer to SGD Gateway |
|
| SGD Gateway to SGD servers |
|
This section includes instructions for configuring the connections used by the SGD Gateway.
The following configuration tasks are described:
Configuring connections between the client device and an SGD Gateway involves the following configuration tasks:
(Optional) Configure the ports and connections used by the SGD Gateway.
You configure these settings when you install the SGD Gateway.
To change these settings, see How to Configure the Ports and Connections for the SGD Gateway.
(Optional) On the SGD Gateway, install an SSL certificate for client connections.
See How to Install an SSL Certificate for Client Connections Into the Client Keystore.
|
You only need to use this procedure if you want to change the settings you made during installation of the SGD Gateway.
Run the gateway config create command.
# /opt/SUNWsgdg/bin/gateway config create |
Answer the on-screen questions, to configure the following:
SGD Gateway port settings. The interface and port used by the SGD Gateway for incoming connections.
Network entry point. The Internet Protocol (IP) address, or Domain Name System (DNS) name, and port that client devices use to connect to the SGD Gateway. This is not always the same as the address of the SGD Gateway. Depending on the configuration of your network, this can be the address of a load balancer or other external device.
Secure connections. Whether to secure the connections between the SGD Gateway and the SGD servers in the array. To use secure connections, the SGD servers in the array must be running in secure mode.
Save the connection and port settings.
The SGD Gateway is configured using the settings you entered.
|
The SSL certificate that the SGD Gateway uses for client connections is called the SGD Gateway SSL certificate. The SSL certificate is stored in the client keystore, /opt/SUNWsgdg/proxy/etc/keystore.client.
By default, the SGD Gateway uses a self-signed SGD Gateway SSL certificate for client connections, but you can replace the self-signed SSL certificate with a certificate signed by a certificate authority (CA).
The following procedure assumes you have an SSL certificate signed by a CA.
The private key you install must be in Privacy Enhanced Mail (PEM) format.
Copy the SSL certificate and the corresponding private key to the SGD Gateway host.
Import the SSL certificate and private key into the client keystore.
Use the gateway sslkey import command, as follows:
# /opt/SUNWsgdg/bin/gateway sslkey import \ --keyfile temp.key \ --keyalg RSA \ --certfile example.com.pem |
Here, the certificate file example.com.pem and the corresponding RSA-encoded private key, temp.key, are imported into the client keystore.
The existing self-signed SSL certificate in the client keystore is overwritten.
Restart the SGD Gateway if you are replacing the SSL certificate on an SGD Gateway that is already configured and running.
Note - Restarting the SGD Gateway disconnects all user sessions and application sessions that are running through the SGD Gateway. |
On the SGD Gateway host, run the following command:
# /opt/SUNWsgdg/bin/gateway restart |
The connections between an SGD Gateway and the SGD servers in the array use certificates for mutual authorization. Configuring these connections involves the following configuration tasks:
Install the SGD Gateway certificate on the SGD array.
See How to Install SGD Gateway Certificates on the SGD Array.
To use this procedure, the SGD servers in the array must be running in secure mode.
See “Setting Up Secure Client Connections (Manual Configuration)” in Chapter 1 of the Sun Secure Global Desktop 4.5 Administration Guide for more information about how to enable security services on an SGD server.
Repeat the following procedure for each SGD server in the array.
Copy the CA certificate from the SGD server to the SGD Gateway keystore directory.
The CA certificate for an SGD server is at /opt/tarantella/var/info/certs/PeerCAcert.pem on the SGD host.
Note - This is the same CA certificate that the SGD server uses for secure intra-array communication. |
The SGD Gateway keystore directory is /opt/SUNWsgdg/proxy/etc.
Copy the SSL certificate from the SGD server to the SGD Gateway keystore directory.
The SSL certificate for an SGD server running in secure mode is at /opt/tarantella/var/tsp/cert.pem on the SGD host.
The SGD Gateway keystore directory is /opt/SUNWsgdg/proxy/etc.
Import the certificates into the SGD Gateway keystore.
# /opt/SUNWsgdg/bin/gateway server add --server sgd-server1 \ --certfile /opt/SUNWsgdg/proxy/etc/PeerCAcert.pem --url https://sgd1.example.com \ --ssl-certfile /opt/SUNWsgdg/proxy/etc/cert.pem |
The --server option defines the alias names used when storing the certificates in the keystore. In this example, the CA certificate is stored using an alias of sgd-server1, the SSL certificate is stored using an alias of sgd-server1-ssl.
https://sgd1.example.com is the Uniform Resource Locator (URL) of the SGD web server.
Note - Restarting the SGD Gateway disconnects all user sessions and application sessions that are running through the SGD Gateway. |
On the SGD Gateway host, run the following command:
# /opt/SUNWsgdg/bin/gateway restart |
Register the SGD Gateway with the SGD array.
Import the SGD Gateway certificate.
$ tarantella gateway add --name sgd-gateway1 \ --certfile /opt/tarantella/var/tsp/gateway1.pem |
where sgd-gateway1 is a name used by SGD to identify the SGD Gateway, and gateway1.pem is the SGD Gateway certificate file name.
To register multiple SGD Gateways at the same time, use the --file option of the tarantella gateway add command. See The tarantella gateway Command for more details.
Configuration changes made using tarantella gateway add are replicated to the other SGD servers in the array.
Configure the SGD Client connections that use the SGD Gateway.
On the primary SGD server, set the --security-gateway global attribute to define which SGD Clients can use the SGD Gateway, based on their IP address or DNS name.
To specify that all SGD Client connections are routed through TCP port 443 of a single SGD Gateway gateway1.example.com, use the following command:
$ tarantella config edit --security-gateway \ "*:sgdg:gateway1.example.com:443" |
To specify that all SGD Client connections are routed through TCP port 443 of an external load balancer lb.example.com, use the following command:
$ tarantella config edit --security-gateway \ "*:sgdg:lb.example.com:443" |
Note - Changes to the --security-gateway attribute affect all SGD servers in the array. The changes only apply to new user sessions. |
See The security-gateway Attribute for more details about how to use the --security-gateway attribute to define multiple SGD Client connection filters.
Configuring connections between the client device and an external load balancer involves the following configuration tasks:
Configuring connections between an external load balancer and the SGD Gateway involves the following configuration tasks:
Configure the ports and connections used by the SGD Gateway.
See How to Configure the Ports and Connections for the SGD Gateway.
(Optional) On the SGD Gateway, install an SSL certificate for incoming client connections.
See How to Install an SSL Certificate for Client Connections Into the Client Keystore.
This section describes how to control the SGD Gateway. The following tasks are described:
To start the SGD Gateway, use the following command:
# /opt/SUNWsgdg/bin/gateway start |
To stop the SGD Gateway, use the following command:
# /opt/SUNWsgdg/bin/gateway stop |
When you use the gateway stop command a warning message is displayed, prompting you to confirm that you want to stop the SGD Gateway. Use the --force option of the gateway stop command if you do not want to display this message.
Note - If the SGD Gateway is stopped, users from outside your network cannot connect to SGD using the SGD Gateway. Client devices that have been enabled using the --security-gateway attribute to access SGD directly without going through the SGD Gateway, can still access SGD. See The security-gateway Attribute. |
To restart the SGD Gateway, use the following command:
# /opt/SUNWsgdg/bin/gateway restart |
When you use the gateway restart command a warning message is displayed, prompting you to confirm that you want to stop the SGD Gateway. Use the --force option of the gateway restart command if you do not want to display this message.
To remove the SGD Gateway, you remove the software installed on the SGD Gateway host.
Change the SGD Client routing configuration for the SGD array.
Edit the --security-gateway attribute for the SGD array.
For a basic deployment using a single SGD Gateway, run the following command:
# tarantella config edit --security-gateway "" |
Note - For a load-balanced deployment using multiple SGD Gateways and an external load balancer, you do not need to edit the --security gateway attribute. |
# /opt/SUNWsgdg/bin/gateway uninstall |
A warning message is displayed, prompting you to confirm that you want to stop the SGD Gateway.
![]() | Caution - The gateway uninstall command is the only supported method of removing the SGD Gateway. Do not use the pkgrm or rpm commands directly to remove the SGD Gateway. |
Remove the SGD Gateway from the list of SGD Gateways registered for the SGD array.
Display the SGD Gateways registered for the SGD array.
# tarantella gateway list Installed gateway: gateway1.example.com Issuer: CN=gateway1.example.com, OU=Marketing, O=Example, L=Boston, ST=Massachusetts, C=US Serial Number: 1208509056 Subject: CN=gateway2.example.com, OU=Marketing, O=Example, L=Boston, ST=Massachusetts, C=US Valid from Fri Sep 26 09:57:36 GMT 2008 to Thu Dec 25 09:57:36 GMT 2008 |
Remove the SGD Gateway from the list of SGD Gateways registered for the SGD array.
# tarantella gateway remove --name gateway1.example.com |
Copyright © 2009, Sun Microsystems, Inc. All rights reserved.