From 3da3a9feffa05f29ab35e0b8048cb7e37a3d4d89 Mon Sep 17 00:00:00 2001 From: fred_the_tech_writer <69817454+fschillingeriv@users.noreply.github.com> Date: Mon, 26 Jul 2021 08:59:21 -0400 Subject: [PATCH] Tweaks (#684) * remove trailing slash * note on saving/backing up recovery codes * add self-hosted servers to list of incrementally updated things --- _articles/getting-started/releasenotes.md | 2 +- _articles/login-with-sso/saml-google.md | 2 +- .../two-step-login/setup-two-step-login-authenticator.md | 6 ++++++ 3 files changed, 8 insertions(+), 2 deletions(-) diff --git a/_articles/getting-started/releasenotes.md b/_articles/getting-started/releasenotes.md index 1ae1cfe1..b8e52d06 100644 --- a/_articles/getting-started/releasenotes.md +++ b/_articles/getting-started/releasenotes.md @@ -21,7 +21,7 @@ Bitwarden believes source code transparency is an absolute requirement for secur ## Release Announcements -**Dates on this page represent Cloud Server and Web releases.** Bitwarden incrementally updates each client application (Desktop, Browser Extension, Mobile, etc.) following the initial release date to ensure feature efficacy and stability. As a result, client applications should expect listed features following the initial release. +**Dates on this page represent Cloud Server and Web releases.** Bitwarden incrementally updates each client application (Desktop, Browser Extension, Mobile, etc.) and for self-hosted servers following the initial release date to ensure feature efficacy and stability. As a result, client applications and self-hosted servers should expect listed features following the initial release. To be notified of Release Announcements, subscribe to the [Bitwarden Status RSS Feed](https://status.bitwarden.com/){:target="\_blank"}. diff --git a/_articles/login-with-sso/saml-google.md b/_articles/login-with-sso/saml-google.md index 4fc20981..9d872483 100644 --- a/_articles/login-with-sso/saml-google.md +++ b/_articles/login-with-sso/saml-google.md @@ -48,7 +48,7 @@ On the Service provider details screen, configure the following fields: |Field|Description| |-----|-----------| |ACS URL|Set this field to the pre-generated **Assertion Consumer Service (ACS) URL** retrieved from the Bitwarden SSO configuration screen.

For Cloud-hosted customers, this is always `https://sso.bitwarden.com/saml2/your-org-id/Acs`. For self-hosted instances, this is determined by your [configured server URL]({{site.baseurl}}/article/install-on-premise/#configure-your-domain), for example `https://your.domain/sso/your-org-id/Acs`.| -|Entity ID|Set this field to the pre-generated **SP Entity ID** retrieved from the Bitwarden SSO Configuration screen.

For Cloud-hosted customers, this is always `https://sso.bitwarden.com/saml2/`. For self-hosted instances, this is determined by your [configured server URL]({{site.baseurl}}/article/install-on-premise/#configure-your-domain), for example `https://your.domain.com/sso/saml2`.| +|Entity ID|Set this field to the pre-generated **SP Entity ID** retrieved from the Bitwarden SSO Configuration screen.

For Cloud-hosted customers, this is always `https://sso.bitwarden.com/saml2`. For self-hosted instances, this is determined by your [configured server URL]({{site.baseurl}}/article/install-on-premise/#configure-your-domain), for example `https://your.domain.com/sso/saml2`.| |Start URL|Optionally, set this field to the login URL from which users will access Bitwarden.

For Cloud-hosted customers, this is always `https://vault.bitwarden.com/#/sso`. For self-hosted instances, this is determined by your [configured server URL]({{site.baseurl}}/article/install-on-premise/#configure-your-domain), for example `https://your.domain.com/#/sso`.| |Signed response|Check this box if you want Workspace to sign SAML responses. If not checked, Workspace will sign only the SAML assertion.| |Name ID format|Set this field to the [SAML NameID format](https://docs.oracle.com/cd/E19316-01/820-3886/ggwbz/index.html){:target="\_blank"} for Workspace to use in SAML responses.| diff --git a/_articles/two-step-login/setup-two-step-login-authenticator.md b/_articles/two-step-login/setup-two-step-login-authenticator.md index 88a11bff..abb10fa8 100644 --- a/_articles/two-step-login/setup-two-step-login-authenticator.md +++ b/_articles/two-step-login/setup-two-step-login-authenticator.md @@ -10,6 +10,12 @@ tags: [two-step login, 2fa, two factor authentication, account, google authentic Two-step Login using a third-party authenticator app (for example, [Authy](https://authy.com/){:target="_blank"}, [Google Authenticator](https://support.google.com/accounts/answer/1066447?hl=en){:target="_blank"}, or [FreeOTP](https://freeotp.github.io/){:target="_blank"}) is available for free to all Bitwarden users. +{% callout info %} +Some authenticator apps, like Google Authenticator, do not automatically backup your 2FA tokens for easy migration to a new mobile device. In these cases, you should manually save the each token's authenticator recovery codes. + +Other apps, like Authy, do support backup and sync across devices. In these cases, be sure to set a strong backup password and keep a record of it in your Bitwarden Vault. +{% endcallout %} + ## Setup an Authenticator Complete the following steps to enable Two-step Login using an authenticator app: