Skip to content

Commit c5811b9

Browse files
author
Rafael Grigorian
committed
Updated features
1 parent b7886b6 commit c5811b9

File tree

6 files changed

+6
-4
lines changed

6 files changed

+6
-4
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This module is available on the <a href="https://marketplace.magento.com/jetrail
1616
- A Master Administrator can overlook every user's authentication process.
1717
- In case of lost or misplaced 2FA account, backup codes are available as an alternate method for authentication.
1818
- In case of an attempted account breach, prevention protocols are in place via Brute-force protection, which will temporarily block the account.
19-
- The threshold for the number of failed authentication attempts before a ban is configurable as well as the number of minutes is temporarily banned for.
19+
- The threshold for the number of failed authentication attempts before a ban is configurable as well as the duration the user is temporarily banned for.
2020
- An automatic instantaneous alert will be sent to the account owner and store admins informing them of an attempted breach. Any security warning will be logged with any relevant data such as the offender's IP address.
2121
- The 2FA account can be setup for devices (something they have) using the Google Authenticator app, which is available for every platform including <a href="https://itunes.apple.com/us/app/google-authenticator/id388497605" >iPhone</a> and <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2" >Android</a>.
2222

design/User Guide.sketch

-17.3 KB
Binary file not shown.

dist/JetRails_TwoFactor-1.1.0.tgz

-57.1 KB
Binary file not shown.
58.9 KB
Binary file not shown.
Binary file not shown.

package.xml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,11 +29,13 @@
2929

3030
- A Master Administrator can require 2FA to be utilized by specific users.
3131
- Usage for 2FA can be enforced and required for log-in.
32-
- Once you use the 2FA to login, there is an option to bypass authentication for 7 days.
32+
- Once you use the 2FA to login, there is an option to bypass authentication for a pre-configured number of days.
33+
- A Master Administrator can overlook every user's authentication process.
3334
- In case of lost or misplaced 2FA account, backup codes are available as an alternate method for authentication.
34-
- In case of at attempted account breach, prevention protocols are in place via Brute Force Protection which will block the account for a set amount of minutes after a set variable number of failed authentication attempts.
35+
- In case of an attempted account breach, prevention protocols are in place via Brute-force protection, which will temporarily block the account.
36+
- The threshold for the number of failed authentication attempts before a ban is configurable as well as the duration the user is temporarily banned for.
3537
- An automatic instantaneous alert will be sent to the account owner and store admins informing them of an attempted breach. Any security warning will be logged with any relevant data such as the offender's IP address.
36-
- The 2FA account can be setup for devices (something they have) using the Google Authenticator app, which is available for every platforms including <a href="https://itunes.apple.com/us/app/google-authenticator/id388497605" >iPhone</a> and <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2" >Android</a>.
38+
- The 2FA account can be setup for devices (something they have) using the Google Authenticator app, which is available for every platforms including iPhone and Android.
3739
</description>
3840
<notes>
3941
- Changed from role based to user based 2FA enforcement

0 commit comments

Comments
 (0)