Red Hat NETWORK 4.0.5 - CLIENT Configuration Manual

Also see for NETWORK 4.0.5 -: Manual Reference guide

Contents

Chapter 2. Client Applications 5--configure, and manually updating the configuration files.( To see how virtually allreconfiguration can be scripted, see Chapter 6 Manually Scripting the Configuration.)2.2.1. Registering with Activation KeysRed Hat recommends using activation keys for registering and configuring client systemsthat access RHN Proxy Server or RHN Satellite Server. Activation keys can be used toregister, entitle, and subscribe systems in a batch. Refer to the Activation Keys section ofthe Red Hat Update Agent chapter within the RHN Management Reference Guide forinstructions on use.Registering with an activation key has four basic steps:1. Generate an Activation Key as described in the Activation Keys section of the RedHat Update Agent chapter within the RHN Management Reference Guide2. Import custom GPG keys.3. Download and install the SSL Certificate RPM from the /pub/ directory of the RHNProxy Server or RHN Satellite Server. The command for this step could look some-thing like this:rpm -Uvh\http://your-satellite.com/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm4. Register the system with your RHN Proxy Server or RHN Satellite Server. The com-mand for this step could look something like:rhnreg_ks --activationkey mykey --serverUrl https://your-satellite.com/XMLRPCAlternatively, most of the above steps can be combined in a shell script that includes thefollowing lines:wget -0 - http://your-satellite-DQDN/pub/bootstrap.sh | bash \&& rhnreg_ks --activation-key my_key --serverUrl \https://your-satellite-FQDN/XMLRPCThe bootstrap script, generated at installation and available for both RHN Satellite Serverand RHN Proxy Server, is such a script. The script and the RHN Bootstrap that generatesit are discussed in detail in Chapter 5 Using RHN Bootstrap.WarningSystems running Red Hat Enterprise Linux 2.1 and versions of Red Hat Linux prior to 8.0may experience problems using Activation Keys to migrate SSL certificate settings fromrhn_register to up2date. Therefore, the SSL certificate information on those systemsmust be set manually. All other settings, such as the server URL, transfer properly.