DOCS: New Guide: Upstream mTLS (#2814)

* rename mtls.md to be client-side specific

* init upstream mTLS guide

* Apply suggestions from code review

Co-authored-by: Travis Groth <travisgroth@users.noreply.github.com>

* clarify assumed config dir

* Apply suggestions from code review

Co-authored-by: bobby <1544881+desimone@users.noreply.github.com>

* link to before-you-begin anchor

* Update docs/guides/upstream-mtls.md

Co-authored-by: Travis Groth <travisgroth@users.noreply.github.com>
Co-authored-by: bobby <1544881+desimone@users.noreply.github.com>
This commit is contained in:
Alex Fornuto 2021-12-27 18:14:18 -06:00 committed by GitHub
parent a4f7bc39a0
commit a95aa7cb77
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 165 additions and 5 deletions

View file

@ -1,15 +1,15 @@
---
title: mTLS
title: Client-Side mTLS
lang: en-US
meta:
- name: keywords
content: pomerium identity-access-proxy mtls client-certificate
description: >-
This guide covers how to use Pomerium to implement mutual authentication
(mTLS) using client certificates with a custom certificate authority.
(mTLS) for end-users, using client certificates with a custom certificate authority.
---
# Implementing mTLS With Pomerium
# Client-Side mTLS With Pomerium
Secure communication on the web typically refers to using signed server certificates with the TLS protocol. TLS connections are both private and authenticated, preventing eavesdropping and impersonation of the server.