mirror of
https://github.com/pomerium/pomerium.git
synced 2025-08-03 08:50:42 +02:00
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:
parent
a4f7bc39a0
commit
a95aa7cb77
5 changed files with 165 additions and 5 deletions
|
@ -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.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue