-
Notifications
You must be signed in to change notification settings - Fork 27
MFA #740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MFA #740
Changes from 7 commits
fc4c86f
249b224
a15b89a
f858f78
5c42a35
77a73ec
c4fdf5f
c9cc838
96850f3
91d247f
e02d774
e6c4c0a
c4387d9
faf9c65
8af4844
4b88630
ccd988d
790120f
361964e
2ea071f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
= Multi-Factor Authentication | ||
|
||
Multi-Factor Authentication (MFA) adds an extra layer of security to your Neo4j Aura account by requiring a verification code in addition to your password. | ||
To generate the verification code use an authenticator app, such as Google Authenticator. | ||
|
||
There's two scenarios for MFA: | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
* Scenario 1: Individual users can enable MFA for their own accounts. | ||
* Scenario 2: Organization administrators can enable MFA for an entire organization, then it's mandatory for all members to go through the MFA setup. | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
== Scenario 1. Enable MFA as a user via account settings | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
[IMPORTANT] | ||
==== | ||
To enable MFA, you must log in using email and password, not Google login or SSO. | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
==== | ||
|
||
. Log in to the Aura Console using your email/password. | ||
. Go to *Account > Settings > Preferences > Security*. | ||
. In the *Multi-Factor Authentication (MFA)* section select *Enable*. | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
. You will be logged out automatically. | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
. Log back in with your email and password. | ||
. A setup modal appears with a QR code. | ||
. Scan the QR code. | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
. Enter the verification code from the authenticator app. | ||
. Save your recovery code somewhere secure. | ||
|
||
|
||
== Scenario 2. Enable MFA for an organization | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
fiquick marked this conversation as resolved.
Show resolved
Hide resolved
|
||
* `Organization Owners` or `Organization Admins` can enable MFA that applies to all members of the organization. | ||
* Members must log in using email and password. MFA setup is not supported for accounts authenticated through SSO or Google OAuth. | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
=== To require MFA for all organization members: | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
. Go to *Account > Settings > Preferences > Security*. | ||
. In the *Multi-Factor Authentication (MFA)* section select *Enable*. | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
==== Member steps to complete MFA setup: | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
. Organization members will see the message, "_Your organization has required Multi Factor Authentication (MFA). Clicking enable MFA below will log you out and you will then need to login using your email and password to configure MFA._" | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
. They click *Enable*. | ||
. Are logged out automatically. | ||
. Log back in using their email and password. | ||
. A setup modal appears with a QR code. | ||
. Using their authenticator app, they scan the QR code. | ||
. Enter the verification code from the authenticator app. | ||
. Save the recovery code somewhere secure. | ||
fiquick marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
Uh oh!
There was an error while loading. Please reload this page.