Enabling and configuring SSL
Enabling SSL
By default, the Anaconda Server installation does not require the use of TLS/SSL certificates. You can enable the use of TLS/SSL after installation by completing the following steps:
-
Edit your
docker-compose.yml
file.-
Find the
Services:
section near the top of the file. Then, under thenginx_proxy:
portion, add the following lines: -
Find the
Keycloak:
section further down in the file. Then, under theenvironment:
portion, add this line:
-
-
Edit your
.env
file.- Change
DOMAIN
to new FQDN, if applicable. - Change
NGINX_PROXY_PORT
to443
. - Change
PROTOCOL
tohttps
- Change
-
Edit your
/opt/anaconda/repo/config/nginx/conf.d/repo.conf
file.-
Near the top of the file, change
listen 8080;
tolisten 8080 ssl;
. -
Add the following lines after the
listen 8080 ssl;
line:
-
-
Add your certificate and private key, named
tls.crt
andtls.key
, to the following directory: -
Run the following command from the directory containing
docker-compose.yml
to apply the changes:
Configuring SSL
The following steps will allow you to configure the SSL:
-
Add or remove the following lines relating to the SSL in
<BASE_INSTALL_DIR>/config/nginx/conf.d/repo.conf
, where<BASE_INSTALL_DIR>
is the installation directory: -
Add or remove certificates from the following directory:
-
Run the following command:
Refer to nginx’s documentation for the standard SSL configuration procedure.
Updating URL/URIs in Keycloak
Once your SSL cert and key are in place, you will need to update Keycloak to point to your new root URL and any valid URI redirects to your domain.
- Navigate to your Keycloak instance at
<FQDN>/auth/admin
and log in. - Select Clients from the left-hand navigation.
- Select repo-service from the list of available clients.
- On the Settings tab, update your root URL and any necessary valid redirect URI’s.
Rebuilding your channel index
Migrating from HTTP
to HTTPS
or updating your FQDN
will alter the file path to your channel’s packages. You must rebuild your channel index to correct the file path. If you do not, you will be unable to successfully download packages after migrating.