Here are some steps to bypass this warning for on-prem users:
Proceed Manually in the Browser:
- Google Chrome/Edge:
- When you see the error, you may get a warning page saying "Your connection is not private" (NET::ERR_CERT_AUTHORITY_INVALID).
- Click "Advanced" (or similar) on the warning page.
- Select "Proceed to [site]" to temporarily bypass the error. This doesn't fix the underlying issue but allows access for the session.
- Firefox:
- Firefox will show a "Warning: Potential Security Risk Ahead" page.
- Click "Advanced," then "Accept the Risk and Continue" to bypass the warning.
- Safari:
- Safari may show "This Connection Is Not Private." Click "Show Details," then "Visit this website," and confirm.
This is the quickest way to access the site without modifying the certificate, but you’ll need to repeat this each time the browser flags the issue.
Add the Self-Signed Certificate as Trusted in Your Browser/OS:
- Export the self-signed certificate from the server hosting your internal software. You can often get this via the browser:
- In Chrome, click the lock icon (or "Not secure") > Certificate > Details > Export.
- In Firefox, click the lock icon > Connection secure > More Information > View Certificate > Download.
- Add the certificate to your browser or operating system’s trusted certificate store:
- Windows:
- Open the certificate file (.cer or .crt), select "Install Certificate," choose "Current User" or "Local Machine," and place it in the "Trusted Root Certification Authorities" store.
- macOS:
- Open Keychain Access, drag the certificate file into the "System" keychain, and set it to "Always Trust" for SSL.
- Linux:
- Add the certificate to the system’s trusted CA store (e.g., /usr/local/share/ca-certificates/) and run sudo update-ca-certificates.
- Windows:
- This makes the browser trust the self-signed certificate without replacing it, but it requires admin access on your machine.
Once you can access the Atomic UI, you can add an ssl certificate by navigating to Administration > HUB SSL Management