Trusted deployments
Why Billet keeps a list of trusted portals, how a portal gets on it, and how to check or remove one.
- For
- Users
- Applies to
- Billet 1.0
- Updated
Each Billet deployment has its own certificate authority, which it uses to prove its relays and hosts are genuine. Billet keeps a trust list of those authorities, one per portal, and checks every new session against it.
How a portal gets on the list
When you sign in to a portal for the first time, Billet fetches that portal's root certificate and adds it to the trust list. You do not normally need to do anything else.
See the list
Open Manage trusted deployments... from the deployment menu at the top left, or the Deployments tab in settings. Each entry shows the portal, the start of its certificate's SHA-256 fingerprint, when it was added, and when the certificate is valid until.
To check an entry is the right one, ask your IT team for the fingerprint of your portal's certificate authority and compare the two.
Add one by hand
Choose Add a deployment, type the portal's address, and press Get its certificate. Billet shows the certificate's fingerprint. Compare it with the one your IT team gives you, then press Trust this deployment.
Remove one
Press Remove beside the entry. New sessions to that deployment fail until it is added again, so only remove a portal you no longer use, or one your IT team has asked you to re-add.
Why a session says the certificate is not trusted
If your organization replaced its certificate authority, the old one on your list no longer matches. Remove the entry and sign in to the portal again, which adds the new one.