BwForCluster User Access/2FA Tokens: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
m (Redirected page to Registration/2FA)
Tag: New redirect
 
(32 intermediate revisions by one other user not shown)
Line 1: Line 1:
#REDIRECT [[Registration/2FA]]

----

'''Currently this description is only valid for bwForCluster JUSTUS 2.'''

----


To improve security a '''2-factor authentication mechanism (2FA)''' is being enforced for logins to the bwForCluster. In addition to the service password a second value, the '''second factor''', has to be entered on every login.


= How 2FA works =

A six-digit auto-generated time-dependent '''One-Time Passwords''' (TOTP) is used. These TOTPs are generated either by a special hardware device ('''hardware token''') or by an application running on a smartphone or computer ('''software token''').

The token has to be synchronized with a central server before it can be used for authentication and then generates an endless stream of six-digit values which can only be used once and are only valid during a very short interval of time. This makes it much harder for potential attackers to access the HPC system, even if they know the regular service password.

== Hardware tokens ==

Hardware tokens are only available for users from the Karlsruhe Institute of Technology (KIT). Every KIT member automatically gets a hardware token when joining the KIT.

<br/>

[[File:2fa token code.jpg|center|frame|Hardware Token used at KIT]]

<br/>

== Software tokens ==

Software tokens (typically an app on your smartphone) are available for all bwHPC users.

'''It is very important that the device that generates the One-Time Passwords and the device which is used to log into the bwForCluster are not the same.''' Otherwise an attacker who gains access to your system can steal both the service password and the secret key of the software token application, which allows them to generate One-Time Passwords and log into the HPC system without your knowledge.

The most common solution is to use a mobile device (e.g. your smartphone or tablet) as a software token by installing one of the following apps:

* FreeOTP for [https://play.google.com/store/apps/details?id=org.fedorahosted.freeotp Android] or [https://apps.apple.com/de/app/freeotp-authenticator/id872559395 iOS]

* Google Authenticator for [https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2 Android] or [https://apps.apple.com/de/app/google-authenticator/id388497605 iOS]

* Microsoft Authenticator for [https://play.google.com/store/apps/details?id=com.azure.authenticator Android] and [https://apps.apple.com/de/app/microsoft-authenticator/id983156458 iOS]

* LastPass Authenticator for [https://play.google.com/store/apps/details?id=com.lastpass.authenticator Android], [https://apps.apple.com/de/app/lastpass-authenticator/id1079110004 iOS] or [https://www.microsoft.com/de-de/p/lastpass-authenticator/9nblggh5l9d7?activetab=pivot:overviewtab Windows]

* Yubico Authenticator for [https://play.google.com/store/apps/details?id=com.yubico.yubioath Android] or [https://apps.apple.com/us/app/yubico-authenticator/id1476679808 iOS]

* andOTP Authenticator for [https://play.google.com/store/apps/details?id=org.shadowice.flocke.andotp Android]

* Aegis Authenticator for [https://play.google.com/store/apps/details?id=com.beemdevelopment.aegis Android]

* Authy for [https://authy.com/download/ Mac, Windows or Linux]

* GNOME Authenticator for [https://github.com/bilelmoussaoui/Authenticator/ Linux]

Open source apps for Android are available via f-droid store: [https://f-droid.org/en/packages/org.shadowice.flocke.andotp/ andOTP Authenticator], [https://f-droid.org/en/packages/com.beemdevelopment.aegis/ Aegis Authenticator] and [https://f-droid.org/en/packages/com.yubico.yubioath/ Yubico Authenticator].

These are only suggestions. You can use any application compatible with the [https://tools.ietf.org/html/rfc6238 TOTP] standard.
<br/>
<br/>

[[File:Freeotp-example.png|center|frame|An example of the FreeOTP app on Android, displaying generated One-Time Passwords for various services]]

= Token Management =

'''bwForCluster tokens''' are generally managed via the '''My Tokens''' menu entry on the central [https://bwidm.scc.kit.edu/ bwIDM registration server]. Here you can register, activate, deactivate and delete tokens.

Usually a TOTP token that has been connected to your account is valid for all clusters on the registration server. Thus you can use the same TOTP token for bwUniCluster 2.0 and JUSTUS 2.

'''KIT users''' can also re-use their existing hardware and software tokens for the HPC systems.


== Registering a new Software or Hardware Token ==

1. First you need to login to the [https://bwidm.scc.kit.edu/ bwIDM registration server] (if you are not logged in already).

2. Select entry '''My Tokens''' in the '''User''' menu.

3. If you have not setup any tokens yet you can directly proceed with step 4 below (since token management is accessible directly for users without tokens). Otherwise (a token is already connected to your account) you need to log into the token management by entering a TOTP and clicking on '''Check'''.

4. Registering a new token starts with a click on '''New smartphone token'''. If you happen to own a USB hardware token device made by the manufacturer '''[https://www.yubico.com Yubikey]''', you can click on '''New Yubikey Token''' instead.

[[File:BwUniCluster 2.0 2fa register new empty.png|center|]]

5. A new windows opens. Click on '''Start''' to generate a new '''QR code'''. This may take a while.

'''NOTE: The QR code contains a key which has to remain secret. Only use the QR code to link your software token app with bwIDM in the next step. Do not save the QR code, print it out or share it with someone else. You can always generate more codes later.'''

[[File:BwUniCluster 2.0 2fa register new qr.png|center|]]

6. Start the software token app on your separate device and scan the QR code. The exact process is a little bit different in every app, but is usually started by pressing on a button with a plus (+) sign or an icon of a QR code.

7. Once the QR code has been loaded into your software token app there should be a new entry called '''bwIDM'''. Generate an One-Time-Password by pressing on this entry or selecting the appropriate button/menu item. You will receive a six-digit code. Enter this code into the field labeled "Current code:" in your bwIDM browser window to prove that the connection has worked and then click on '''Check'''.

8. If everything worked as expected, you will be returned to the '''My Tokens''' screen and there will be a new entry for your Software Token:

[[File:BwUniCluster 2.0 2fa register new success.png|center|]]

9. Repeat the process to register additional tokens. '''Please register at least a Backup TAN list in addition to the hardware/software token you plan to use regularly.''' If you only register a single token and happen to lose access to it, e.g. because you lose your device, uninstall the software token application or data gets deleted/corrupted, you will neither be able to log into the cluster system nor register a new token. In such a case please follow instructions of the next section.

= Recovery when access to all tokens has been lost =

To gain access again after you have lost access to all your tokens including the backup TAN list, please contact the [[BwForCluster_JUSTUS_Contact_and_Support|JUSTUS 2 support]] via bwSupport Portal '''(NOT email !!!)''' and ask for reset of all your TOTP tokens. This process will take its time.

= Deactivating a Token =

Click on the '''Disable''' button next to the Token entry on the '''My Tokens''' screen.

= Deleting a Token =

After a Token has been disabled a new button labeled '''Delete''' will appear. Click on it to delete the Token.

Latest revision as of 18:05, 17 February 2022

Redirect to:

Retrieved from "https://wiki.bwhpc.de/wiki/index.php?title=BwForCluster_User_Access/2FA_Tokens&oldid=10050"