Streamline SSL layer for better X509 infrastructure support

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Security
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Instead of having separate CA vs CusterCA, we should have a single CA with role separation: e.g.: allow specifying limitations on which CA can be used for what purpose. Specifically, to pin X509 authorization to a specific roots only

            Assignee:
            [DO NOT USE] Backlog - Security Team
            Reporter:
            Sergey Galtsev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: