1
0
mirror of https://github.com/bitwarden/help synced 2025-12-06 00:03:30 +00:00

update diagrams (#826)

This commit is contained in:
fred_the_tech_writer
2021-12-13 09:34:32 -05:00
committed by GitHub
parent adc86d8749
commit 1d43b8860c
4 changed files with 2 additions and 2 deletions

View File

@@ -15,7 +15,7 @@ Key Connector is a self-hosted application that facilitates **Customer-managed E
Key Connector requires connection to a **database where encrypted user keys are stored** and an **RSA Key Pair to encrypt and decrypt stored user keys**. Key Connector can be [configured]({{site.baseurl}}/article/deploy-key-connector/) with a variety of both database providers (e.g. MSSQL, PostgreSQL, MySQL) and Key Pair storage providers (e.g. Hashicorp Vault, Cloud KMS Providers, On-prem HSM devices) in order to fit your business' infrastructure requirements.
{% image sso/keyconnector/keyconnector-diagram.png Key Connector Architecture %}
{% image sso/keyconnector/keyconnector-diagram-2.png Key Connector Architecture %}
## Why use Key Connector?

View File

@@ -19,7 +19,7 @@ What makes Login with SSO unique is that it retains our zero-knowledge encryptio
In most scenarios, that decryption key is the user's [Master Password]({{site.baseurl}}/article/master-password/), which they retain sole responsibility for, however Organizations self-hosting Bitwarden can use [Key Connector]({{site.baseurl}}/article/about-key-connector/) as an alternative means of decrypting Vault data.
{% image sso/sso-workflow-2.png Login with SSO & Master Password Decryption %}
{% image sso/sso-workflow-3.png Login with SSO & Master Password Decryption %}
## Why use Login with SSO?