moodLearning Wiki

Trace: › router-notes › ui-design-principles › internship-tips › elearning-faqs › 2-factor-authentication

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
2-factor-authentication [2018/04/24 08:52]
ton [LMS] 		2-factor-authentication [2020/06/13 15:10] (current)
Line 1: Line 1:
 +[[lms-security|{{ ::lmssecurity.jpg?400 |}}]]
 ====== 2-factor authentication ====== ====== 2-factor authentication ======
 ===== LMS ===== ===== LMS =====
 Steps in activating two-factor authentication on moodLearning-powered learning management system (LMS): \\ Steps in activating two-factor authentication on moodLearning-powered learning management system (LMS): \\
 \\ \\
- +==== Administrator ==== 
-1. Login as Administrator to the LMS. As admin, you are not required to fill in the token field so you can just leave the token field empty.+1. Login as **Administrator** to the LMS. As admin, you are not required to fill in the token field so you can just leave the token field empty.
  
 2. After a successful login, select now a user you want to use Two-Factor Authentication by navigating your way to //Site Administration// > //Accounts// > //Browse List of Users//:  2. After a successful login, select now a user you want to use Two-Factor Authentication by navigating your way to //Site Administration// > //Accounts// > //Browse List of Users//: 
  
-{{:capture.png?400|}}+{{ ::capture.png?300 |}}
  
 From here simply click the gear icon on the user to redirect you to the user's profile editing page. From here simply click the gear icon on the user to redirect you to the user's profile editing page.
Line 14: Line 15:
 3. Next is to set the authentication method to **A2FA (Anonther 2-Factor Auth)**. 3. Next is to set the authentication method to **A2FA (Anonther 2-Factor Auth)**.
  
-{{:auth1.png?400|}}+{{ ::auth1.png?200 |}}
  
 To generate the QR code for the user, scroll down to **Other fields** and click the //Generate new secret// button  To generate the QR code for the user, scroll down to **Other fields** and click the //Generate new secret// button 
  
-{{:generate.png?400|}}+{{ ::generate.png?200 |}}
  
 Then click Update Profile to save the new setting. Then click Update Profile to save the new setting.
Line 24: Line 25:
 4. To check for the generated QR code, go to the user's profile you've just updated.  4. To check for the generated QR code, go to the user's profile you've just updated. 
  
-{{:qr_code.png?600|}} +{{ ::qr_code.png?200 |}} 
  
 You may now use the snipping tool or any screen capturing tool and send this QR image to your user. Currently sending QR code images are done manually.  You may now use the snipping tool or any screen capturing tool and send this QR image to your user. Currently sending QR code images are done manually. 
 +\\ 
 +\\ 
 +==== User ====
 5. If admin failed to send the QR code, the user may click the //Re-send token to your email instead?// after filling in the fields username and password in the login page.  5. If admin failed to send the QR code, the user may click the //Re-send token to your email instead?// after filling in the fields username and password in the login page. 
-{{:logintoken.png?600|}}+{{ ::logintoken.png?200 |}}
 The system will prompt if the link to the token is already sent to the user's email address. The system will prompt if the link to the token is already sent to the user's email address.
  
-6. The user will just have to follow the link provided in the email then copy the token provided  +6. The user will just have to follow the link provided in the email then copy the token provided and paste it to the token field in the login page. Beware of the 30 seconds timeout. 
-{{:code.png?600|}}+{{ ::code.png?200 |}}
  
  
-5. Now if the user is now in his account, he may just go to his profile to scan the QR code with //Google authenticator//.  Make sure your mobile device is connected to the internet during this process.+7. If the user is now in his account, he may just need to go to his profile to scan the QR code with //Google authenticator//.  Make sure the mobile device is connected to the internet during this process.
  
-{{:screenshot_20180418-164010.jpg?400|}}+{{ ::screen_shot_2018-05-08_at_4.48.24_am.png?200 |}}
  
-{{:screenshot_20180418-164215.jpg?400|}}+{{ ::screenshot_20180418-164215.jpg?200 |}}
  
-{{:screenshot_20180418-164219.jpg?400|}}+{{ ::screenshot_20180418-164219.jpg?200 |}}
  
-After you register the QR code, copy the token provided and add this to the token field in the login page.  Note that the token is only available for 30 seconds. +After the QR code is registered, copy the token provided and add this to the token field in the login page.  Again, the token is only available for 30 seconds.
- +
-6. Now try to login the user with the token provided by the authenticator.  +
-{{:token.png?400|}} +
- +
  
 +8. Now try to login the user with the token provided by the authenticator. 
 +{{ ::token.png?200 |}}
 \\ \\
 \\ \\
 +===2-Factor Authentication FAQs===
 +  * [[2-Factor Authentication FAQs]]
 +\\
 +\\
 +===== Content Management System===== 
 +A similar measure could be put in place for moodLearning-powered CMS. Example here:
 +\\
 +{{ ::2-factor_auth-for-cms.png?200 |}}
 +\\
 +====== See Also ======
 +  * [[LMS Security]]
 +
 +----
Last modified: 2020/06/13 15:11