1
edit
Changes
no edit summary
1) Create an NSS database on the bridge, to hold the certificate information *AS user '''sigul''' issue the following
* login as sigul:
su -s /bin/bash sigul
* generate a new NSS database for the bridge at the location of the bridge_dir variable bridge_dir=/var/lib/sigul <-- This variable should be set to the location where sigul resides on the system certutil -d $bridge_dir -N <-- This will generate a new NSS database for the bridge at the location of the bridge_dir variable
[Be sure to remember your NSS Password]
5) After editing the config and setting up the certs, it is time for a test drive issue the following * AS '''ROOT''':
* start the bridge in DEBUG mode, and all information will be logged in ''/var/log/sigul_bridge.log'':
* check the log file after starting sigul, if there are no errors you are good to go.
** you should see the first log message in ''/var/log/sigul_bridge.log'':
To begin setup, we have to follow a similar process to the bridge with NSS, except that we will import the CA cert generated on the bridge, not generate a new one.
Add bridge hostname to /etc/hosts:
[IP address of the bridge] sigul-bridge-hostname
1) Create the NSS database on the server, to hold the certificate information *AS user '''sigul''' issue the following
* login as sigul:
su -s /bin/bash sigul
* The sigul CA certs should now be imported
* be sure to replace SERVER_HOSTNAME with the hostname of the machine it resides on.:
certutil -d $server_dir -S -n sigul-server-cert -s 'CN=SERVER_HOSTNAME' -c my-ca -t u,, -v 120
What the client does: The client is simply that, a client, it has certs necessary for it to be authenticated with the sigul bridge to issue commands as the sigul admin, to the server. All client commands are sent to bridge which in turn talks to either koji or the server depending on what the clients request is.
Add hostnames to /etc/hosts:
[IP address of the bridge] sigul-bridge-hostname
[IP address of the server] sigul-server-hostname
To begin setup, we have to follow a similar process to the bridge with NSS, except that we will import the CA cert generated on the bridge, not generate a new one.