Once you finished installing Replicated, the installer gave you a link that can be used to finish configuring the Replicated administration console. Please open a browser and go to this link. If you have forgotten the link, it is most likely https://<ip address>:8800.
Step One: Configuring HTTPS for the Administration Console
You will be presented with the following screen:
As you can see, you are being asked to provide a hostname, a private key, and a certificate. You are also provided with two options to move forward:
- Upload & Continue: This allows you to upload the private key and certificate file you wish the web server to use for SSL. This is highly recommended.
- Use Self-Signed Cert: Use this if you want the system to generate an SSL certificate for the hostname provided. If you choose this, users will have to accept this certificate.
The following values should be given:
- Hostname: This is the DNS hostname that you wish administrators and users to use to access the system. For example, if you want the system to be https://gitprime.mycompany.com, you should enter gitprime.mycompany.com
- Private Key: The private key of the SSL certificate to use in PEM format.
- Certificate: The certificate you wish to used, in PEM format
Step Two: Uploading Your License
You will have been provided with a license file by your sales representative or customer support. This file will end with the file extension ".rli" and will most likely be the name of your company. Please upload that file here:
Step Three: Choose Your Installation Type
If you have a license that allows airgapped installations, you will now be asked to choose your installation type. If you are not, you may skip ahead to Step Four.
However, if you are allowed airgapped installations, you will be presented with the following screen.
Standard Installation Type: License Activation
For the standard installation method, you will be asked to activate your license. The system will send an e-mail to the user that is registered in the license. Find that key in your e-mail and enter it in this screen:
You may now continue to Step Four.
Airgapped Package Upload
If you are following the airgapped installation method, you will be asked to upload your airgapped package. You should have already created an upload directory and uploaded the airgapped package to the server. Now, on the screen presented, you should enter the full path to that file. For example, "/var/lib/replicated/updates/GitPrime Enterprise - 133.airgap".
Once you have clicked Continue, the system will begin to validate and load your airgapped package:
When it is complete, you will be asked to secure the administration console. You may now continue to Step Four
Step Four: Secure the Administration Console
You will be asked to secure the administration console. At this point, you will have three options:
- Password: This sets a single password that can be shared across administrators. This is the default.
- LDAP: If you want to integrate the system with your LDAP or Active Directory based security, choose this option.
- Anonymous: Means that anyone can utilize the administration console. This is NOT recommended for production use.
Choose your option from the following screen:
If you choose this option, generate a password that meets your company's password security policies and record it for use. Enter it into both fields and click Continue to move to the next step.
If you choose to use LDAP, you will be presented with a large number of options. We recommend that you implement LDAP authentication only if you are very knowledgeable about your LDAP directory server and its layout.
If you choose the highly insecure Anonymous option, you can click Continue to move to the next step.
Step Five: Preflight Checks
This screen shows you all the checks that the system performs to validate that it can run. If any dependencies are not met, they will be called out in red. This screen looks like:
Once you have validated that these checks are correct, you may choose to re-run the checks (if you've corrected them) or proceed anyway, ignoring any warnings.
Note: You should not skip warnings and errors here. Modify the system to meet proper specifications, especially for production machines.
Once you have validated the settings and conditions, you may continue on to Configuring Flow Enterprise.
If you need help, please email email@example.com for 24/7 assistance.