• 
      

    Add a guide and glossary on SSL/TLS configuration.

    Review Request #15065 — Created May 18, 2026 and submitted

    Information

    Review Board
    release-8.x

    Reviewers

    This adds a new docs page covering how to manage SSL/TLS certificates
    and CA bundles. As of Review Board 8, these need to be configured
    manually on the filesystem. This guide walks through how to do that, and
    the various SSL options available.

    Since there's a lot of terms thrown around, the glossary has been
    updated to flesh out these terms and link back to this page.

    In the future, this page will be a good place to document the cert
    configuration UI and cert synchronization, once that's been written.

    Checked for obvious spelling, link, or build errors. Ran it through
    Claude to check for any notable issues.

    Summary ID
    Add a guide and glossary on SSL/TLS configuration.
    This adds a new docs page covering how to manage SSL/TLS certificates and CA bundles. As of Review Board 8, these need to be configured manually on the filesystem. This guide walks through how to do that, and the various SSL options available. Since there's a lot of terms thrown around, the glossary has been updated to flesh out these terms and link back to this page. In the future, this page will be a good place to document the cert configuration UI and cert synchronization, once that's been written.
    7d08121ff5fbdcacb0da4f308dfc246780b21d98
    Description From Last Updated

    Instead of "they should also be lowercase", maybe "and the hostname must be lowercase" ?

    david david

    Based on our matching this should be all first-level subdomains. We might want to clarify that and add a note …

    david david

    There's an extra "*" in here.

    david david

    Either we should have a term for "Private Key" or we should lowercase it.

    david david
    david
    1. 
        
    2. Show all issues

      Instead of "they should also be lowercase", maybe "and the hostname must be lowercase" ?

    3. Show all issues

      Based on our matching this should be all first-level subdomains. We might want to clarify that and add a note that nested subdomains will require their own cert.

      1. It supports subdomains. You just can't have a wildcard in the middle of a domain. *.corp.example.com is valid and in the test data. svn.*.example.com is not valid. I can document the wildcard placement.

    4. docs/manual/glossary.rst (Diff revision 1)
       
       
      Show all issues

      There's an extra "*" in here.

    5. docs/manual/glossary.rst (Diff revision 1)
       
       
      Show all issues

      Either we should have a term for "Private Key" or we should lowercase it.

    6. 
        
    chipx86
    david
    1. Ship It!
    2. 
        
    chipx86
    Review request changed
    Status:
    Completed
    Change Summary:
    Pushed to release-8.x (8e74a20)