mirror of
https://github.com/bitwarden/help
synced 2025-12-12 14:23:15 +00:00
→ all ->
This commit is contained in:
@@ -63,7 +63,7 @@ If you are having trouble getting the YubiKey NEO to work on your Android device
|
|||||||
|
|
||||||
1. You have checked the **One of my keys supports NFC** checkbox from step 5 above.
|
1. You have checked the **One of my keys supports NFC** checkbox from step 5 above.
|
||||||
2. Your Android device [supports NFC](https://en.wikipedia.org/wiki/List_of_NFC-enabled_mobile_devices){:target="_blank"} and is [known to work properly](https://forum.yubico.com/viewtopic.php?f=26&t=1302){:target="_blank"} with YubiKey NEO.
|
2. Your Android device [supports NFC](https://en.wikipedia.org/wiki/List_of_NFC-enabled_mobile_devices){:target="_blank"} and is [known to work properly](https://forum.yubico.com/viewtopic.php?f=26&t=1302){:target="_blank"} with YubiKey NEO.
|
||||||
3. You have NFC enabled on your Android device. Enable NFC by going to Android **Settings** -> **More** and enable the **NFC** option.
|
3. You have NFC enabled on your Android device. Enable NFC by going to Android **Settings** → **More** and enable the **NFC** option.
|
||||||
|
|
||||||
If the YubiKey NEO can be used on your Android device you will be prompted with a YubiKey option while logging in to bitwarden. Simply place the YubiKey NEO on the back of your Android device near the NFC receiver. If you do not know where your NFC receiver is located, you may need to move it around some, trying different areas. Once bitwarden detects the YubiKey it will automatically validate and log you in.
|
If the YubiKey NEO can be used on your Android device you will be prompted with a YubiKey option while logging in to bitwarden. Simply place the YubiKey NEO on the back of your Android device near the NFC receiver. If you do not know where your NFC receiver is located, you may need to move it around some, trying different areas. Once bitwarden detects the YubiKey it will automatically validate and log you in.
|
||||||
|
|
||||||
|
|||||||
@@ -42,7 +42,7 @@ If you already have a Google Cloud project available, you can skip this step and
|
|||||||
|
|
||||||
1. Go to <https://console.cloud.google.com>
|
1. Go to <https://console.cloud.google.com>
|
||||||
2. Make sure the appropriate project is selected.
|
2. Make sure the appropriate project is selected.
|
||||||
3. Open the navigation menu and navigate to **API Manager** -> **Dashboard**.
|
3. Open the navigation menu and navigate to **API Manager** → **Dashboard**.
|
||||||
4. Select the **Enable API** button near the top.
|
4. Select the **Enable API** button near the top.
|
||||||
{% image directory-connector/gsuite/enable-api.png %}
|
{% image directory-connector/gsuite/enable-api.png %}
|
||||||
5. Click the **Admin SDK** link under the **Google Apps APIs** section.
|
5. Click the **Admin SDK** link under the **Google Apps APIs** section.
|
||||||
@@ -54,7 +54,7 @@ If you already have a Google Cloud project available, you can skip this step and
|
|||||||
|
|
||||||
1. Go to <https://console.cloud.google.com>
|
1. Go to <https://console.cloud.google.com>
|
||||||
2. Make sure the appropriate project is selected.
|
2. Make sure the appropriate project is selected.
|
||||||
3. Open the navigation menu and navigate to **API Manager** -> **Credentials**.
|
3. Open the navigation menu and navigate to **API Manager** → **Credentials**.
|
||||||
4. Click the **Create credentials** button and select **Service account key**.
|
4. Click the **Create credentials** button and select **Service account key**.
|
||||||
{% image directory-connector/gsuite/create-credentials.png %}
|
{% image directory-connector/gsuite/create-credentials.png %}
|
||||||
5. Select **New service account**.
|
5. Select **New service account**.
|
||||||
@@ -76,7 +76,7 @@ If you already have a Google Cloud project available, you can skip this step and
|
|||||||
2. Open the navigation menu and navigate to **Security**.
|
2. Open the navigation menu and navigate to **Security**.
|
||||||
3. Select the **API reference** option and make sure **Enable API access** is checked.
|
3. Select the **API reference** option and make sure **Enable API access** is checked.
|
||||||
{% image directory-connector/gsuite/enable-api-access.png %}
|
{% image directory-connector/gsuite/enable-api-access.png %}
|
||||||
4. Back in the list of options, select **Show more** -> **Advanced settings** -> **Manage API client access**
|
4. Back in the list of options, select **Show more** → **Advanced settings** -> **Manage API client access**
|
||||||
{% image directory-connector/gsuite/manage-api-access.png %}
|
{% image directory-connector/gsuite/manage-api-access.png %}
|
||||||
5. For **Client Name**, paste the **Client ID** of the service account that you created in the previous steps. For **API Scopes**, paste the following values to grant read-only access to users and groups:
|
5. For **Client Name**, paste the **Client ID** of the service account that you created in the previous steps. For **API Scopes**, paste the following values to grant read-only access to users and groups:
|
||||||
<pre>https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.group.readonly,https://www.googleapis.com/auth/admin.directory.group.member.readonly</pre>
|
<pre>https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.group.readonly,https://www.googleapis.com/auth/admin.directory.group.member.readonly</pre>
|
||||||
|
|||||||
@@ -12,11 +12,11 @@ You can use the bitwarden Android app to add new and auto-fill existing logins o
|
|||||||
## Enabling the service
|
## Enabling the service
|
||||||
|
|
||||||
1. Open the bitwarden Android app.
|
1. Open the bitwarden Android app.
|
||||||
2. Tap **Tools** -> **bitwarden Auto-fill Service**. Status *Disabled* will appear.
|
2. Tap **Tools** → **bitwarden Auto-fill Service**. Status *Disabled* will appear.
|
||||||
3. Tap **Open Accessibility Settings**.
|
3. Tap **Open Accessibility Settings**.
|
||||||
4. Locate **bitwarden** from the list and enable it.
|
4. Locate **bitwarden** from the list and enable it.
|
||||||
|
|
||||||
Auto-fill is context-sensitive. This means that the bitwarden auto-fill icon, and notification will only appear when the app detects a login form. You can change the way auto-fill behaves by navigating to **Settings** -> **Features** -> **Auto-fill**.
|
Auto-fill is context-sensitive. This means that the bitwarden auto-fill icon, and notification will only appear when the app detects a login form. You can change the way auto-fill behaves by navigating to **Settings** → **Features** → **Auto-fill**.
|
||||||
|
|
||||||
## Testing auto-fill
|
## Testing auto-fill
|
||||||
|
|
||||||
|
|||||||
@@ -13,7 +13,7 @@ As a workaround, if you are looking to auto-fill a login while in Firefox Privat
|
|||||||
|
|
||||||
1. Navigate to the website's login page in Firefox Private Browsing.
|
1. Navigate to the website's login page in Firefox Private Browsing.
|
||||||
2. Right click the page. A context menu will appear.
|
2. Right click the page. A context menu will appear.
|
||||||
3. Select **bitwarden -> Auto-fill -> [your login]**.
|
3. Select **bitwarden** → **Auto-fill → **[your login]**.
|
||||||
|
|
||||||
Alternatively, you can also copy/paste your login credentials by accessing your vault from the regular, non-private browsing mode.
|
Alternatively, you can also copy/paste your login credentials by accessing your vault from the regular, non-private browsing mode.
|
||||||
|
|
||||||
|
|||||||
@@ -23,7 +23,7 @@ Once you invite a user they will receive an email where they will need to click
|
|||||||
|
|
||||||
{% image organizations/user-accept.png %}
|
{% image organizations/user-accept.png %}
|
||||||
|
|
||||||
After the user has successfully accepted the organization invite, an organization admin will then need to **confirm** the user from the same area in the web vault that you invited the user from (Organization Admin -> People). Only after the user is confirmed will they then have access to that organization and the items being shared with them.
|
After the user has successfully accepted the organization invite, an organization admin will then need to **confirm** the user from the same area in the web vault that you invited the user from (Organization Admin → People). Only after the user is confirmed will they then have access to that organization and the items being shared with them.
|
||||||
|
|
||||||
{% image organizations/org-people-options.png %}
|
{% image organizations/org-people-options.png %}
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user