BinAC/Login - Revision history

S Behnle at 15:45, 5 May 2025

2025-05-05T15:45:43Z

← Older revision		Revision as of 17:45, 5 May 2025
Line 27:		Line 27:
	</pre>		</pre>

	where the <code>UserID</code> has to follow the [[Registration/Login/Username\|username convention]] (also see below). The QR code displayed on screen must be scanned with your authenticator app. Note, the QR code is only displayed once. If you need a new QR code , please contact us (hpcmaster@uni-tuebingen.de) to reset the procedure.		where the <code><UserID></code> has to follow the [[Registration/Login/Username\|username convention]] (also see below). The QR code displayed on screen must be scanned with your authenticator app. Note, the QR code is only displayed once. If you need a new QR code , please contact us (hpcmaster@uni-tuebingen.de) to reset the procedure.
	Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.		Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.

S Behnle: Clarified the username to use

2025-05-05T15:44:29Z

Clarified the username to use

← Older revision		Revision as of 17:44, 5 May 2025
Line 27:		Line 27:
	</pre>		</pre>

	The QR code displayed on screen must be scanned with your authenticator app. Note, the QR code is only displayed once. If you need a new QR code , please contact us (hpcmaster@uni-tuebingen.de) to reset the procedure.		where the <code>UserID</code> has to follow the [[Registration/Login/Username\|username convention]] (also see below). The QR code displayed on screen must be scanned with your authenticator app. Note, the QR code is only displayed once. If you need a new QR code , please contact us (hpcmaster@uni-tuebingen.de) to reset the procedure.
	Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.		Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.

K Siegmund: /* Related Information */

2024-11-05T09:55:03Z

Related Information

← Older revision		Revision as of 11:55, 5 November 2024
Line 156:		Line 156:
	* If you want to register a new token for the two factor authentication (2FA), consult [[BinAC/Login#TOTP_Second_Factor\|this section]].		* If you want to register a new token for the two factor authentication (2FA), consult [[BinAC/Login#TOTP_Second_Factor\|this section]].
	* If you want to de-register, consult the [[Registration/Deregistration\|De-registration Guide]].		* If you want to de-register, consult the [[Registration/Deregistration\|De-registration Guide]].
			* Configuring your shell: [[.bashrc Do's and Don'ts]]

	<!--* If you need an SSH key for your workflow, read [[Registration/SSH\|Registering SSH Keys with your Cluster]].-->		<!--* If you need an SSH key for your workflow, read [[Registration/SSH\|Registering SSH Keys with your Cluster]].-->

F Bartusch at 13:39, 8 December 2022

2022-12-08T13:39:32Z

Show changes

F Bartusch at 09:56, 6 December 2022

2022-12-06T09:56:03Z

← Older revision		Revision as of 11:56, 6 December 2022
Line 103:		Line 103:

	* Compute jobs must be submitted as [[Batch Jobs]]		* Compute jobs must be submitted as [[Batch Jobs]]


	----
	[[Category:BwForCluster BinAC]]
	[[Category:BwForCluster BinAC\|Access]]
	[[Category:BwForCluster BinAC\|Login]]
	[[Category:Access\|bwForCluster BinAC]]

F Bartusch: F Bartusch moved page BwForCluster BinAC Login to BinAC/Login

2022-08-04T08:07:20Z

F Bartusch moved page BwForCluster BinAC Login to BinAC/Login

← Older revision	Revision as of 10:07, 4 August 2022
(No difference)

F Bartusch at 15:45, 20 January 2022

2022-01-20T15:45:48Z

← Older revision		Revision as of 17:45, 20 January 2022
Line 2:		Line 2:

	After registration (registration procedure at [[bwForCluster User Access]], the bwForCluster BinAC can be accessed via a Secure Shell like <tt>ssh</tt> on Linux and Mac or <tt>PuTTY</tt> on Windows systems.		After registration (registration procedure at [[bwForCluster User Access]], the bwForCluster BinAC can be accessed via a Secure Shell like <tt>ssh</tt> on Linux and Mac or <tt>PuTTY</tt> on Windows systems.

			{\|style="background:#deffee; width:100%;"
			\|style="padding:5px; background:#cef2e0; text-align:left"\|
			[[Image:Attention.svg\|center\|25px]]
			\|style="padding:5px; background:#cef2e0; text-align:left"\|
			Login is only possible through university networks! If you're at home or abroad, you will need to use your university's VPN.
			\|}

	== TOTP Second Factor ==		== TOTP Second Factor ==

F Bartusch at 13:22, 21 October 2020

2020-10-21T13:22:26Z

← Older revision		Revision as of 15:22, 21 October 2020
Line 6:		Line 6:
	Install a TOTP (time-based one-time password) app to your mobile device such as Google, Microsoft, andOTP, Aegis, FreeOTP, or Yubico Authenticator. These apps work very similar and allow you to scan a QR code containing a secret key used for the TOTP password generation.		Install a TOTP (time-based one-time password) app to your mobile device such as Google, Microsoft, andOTP, Aegis, FreeOTP, or Yubico Authenticator. These apps work very similar and allow you to scan a QR code containing a secret key used for the TOTP password generation.

			Connect to the QR code server and enter your password.
⚫	~~Connect to the QR code server, e.g. ssh tu_iis4711@c2fa.binac.uni-tuebingen.de and enter your username and password.~~ The QR code displayed on screen must be scanned with your authenticator app. Note, the QR code is only displayed once. If you need a new QR code , please contact us (hpcmaster@uni-tuebingen.de) to reset the procedure.

			<pre>
			ssh <UserID>@c2fa.binac.uni-tuebingen.de
			</pre>

		⚫	The QR code displayed on screen must be scanned with your authenticator app. Note, the QR code is only displayed once. If you need a new QR code , please contact us (hpcmaster@uni-tuebingen.de) to reset the procedure.
	Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.		Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.

	== Login ==		== Login ==
	You may use the nodes login01.binac.uni-tuebingen.de and login02.binac.uni-tuebingen.de to access the BinAC e.g~~. ssh <UserID>@login01.binac.uni-tuebingen.de or ssh <UserID>@login02.binac.uni-tuebingen.de. You will be asked for the 6-digit second factor and afterwards for username and password~~.		You may use the nodes login01.binac.uni-tuebingen.de and login02.binac.uni-tuebingen.de to access the BinAC e.g.

			<pre>
			ssh <UserID>@login01.binac.uni-tuebingen.de # or
			ssh <UserID>@login02.binac.uni-tuebingen.de # or
			ssh <UserID>@login03.binac.uni-tuebingen.de
			</pre>

			You will be asked for the 6-digit second factor and afterwards for your password.
	If you mistype the password after entering the correct 6-digit second factor you have to wait for 30 seconds till a new second factor is generated, as it is truly a time-based one-time password and cannot be used again.		If you mistype the password after entering the correct 6-digit second factor you have to wait for 30 seconds till a new second factor is generated, as it is truly a time-based one-time password and cannot be used again.

J Krueger at 08:22, 16 July 2020

2020-07-16T08:22:34Z

← Older revision		Revision as of 10:22, 16 July 2020
Line 3:		Line 3:
	After registration (registration procedure at [[bwForCluster User Access]], the bwForCluster BinAC can be accessed via a Secure Shell like <tt>ssh</tt> on Linux and Mac or <tt>PuTTY</tt> on Windows systems.		After registration (registration procedure at [[bwForCluster User Access]], the bwForCluster BinAC can be accessed via a Secure Shell like <tt>ssh</tt> on Linux and Mac or <tt>PuTTY</tt> on Windows systems.

			== TOTP Second Factor ==
	From linux machines, you can log in using
			Install a TOTP (time-based one-time password) app to your mobile device such as Google, Microsoft, andOTP, Aegis, FreeOTP, or Yubico Authenticator. These apps work very similar and allow you to scan a QR code containing a secret key used for the TOTP password generation.

			Connect to the QR code server, e.g. ssh tu_iis4711@c2fa.binac.uni-tuebingen.de and enter your username and password. The QR code displayed on screen must be scanned with your authenticator app. Note, the QR code is only displayed once. If you need a new QR code , please contact us (hpcmaster@uni-tuebingen.de) to reset the procedure.
	ssh <UserID>@login01.binac.uni-tuebingen.de
			Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.
	ssh <UserID>@login02.binac.uni-tuebingen.de
	ssh <UserID>@login03.binac.uni-tuebingen.de

			== Login ==
	To run graphical applications, you can use the -X or -Y flag to openssh:
			You may use the nodes login01.binac.uni-tuebingen.de and login02.binac.uni-tuebingen.de to access the BinAC e.g. ssh <UserID>@login01.binac.uni-tuebingen.de or ssh <UserID>@login02.binac.uni-tuebingen.de. You will be asked for the 6-digit second factor and afterwards for username and password.

			If you mistype the password after entering the correct 6-digit second factor you have to wait for 30 seconds till a new second factor is generated, as it is truly a time-based one-time password and cannot be used again.
	ssh -Y -l <UserID> login01.binac.uni-tuebingen.de
	ssh -Y -l <UserID> login02.binac.uni-tuebingen.de
	ssh -Y -l <UserID> login03.binac.uni-tuebingen.de

	For better performance on slow connections you should use e.g. [[VNC]].

			== SSH Keys (optional) ==
			You may use SSH keys to access the login nodes. It is mandatory to secure your private key with a password. Place your public key into ~/.ssh/authorized_keys and take care about line breaks.
			If you are using services which require automated password less login, contact us hpcmaster@uni-tuebingen.de. We are working on appropriate solutions and will adopt them individually.

	== About UserID / Username ==		== About UserID / Username ==

F Bartusch: /* About UserID / Username */

2020-06-05T12:16:07Z

About UserID / Username

← Older revision		Revision as of 14:16, 5 June 2020
Line 58:		Line 58:
	\|Tübingen		\|Tübingen
	\|tu		\|tu
			\|tu_username
	\|username
	\|-		\|-
	\|Ulm		\|Ulm

← Older revision		Revision as of 11:55, 5 November 2024
Line 156:		Line 156:
	* If you want to register a new token for the two factor authentication (2FA), consult [[BinAC/Login#TOTP_Second_Factor\|this section]].		* If you want to register a new token for the two factor authentication (2FA), consult [[BinAC/Login#TOTP_Second_Factor\|this section]].
	* If you want to de-register, consult the [[Registration/Deregistration\|De-registration Guide]].		* If you want to de-register, consult the [[Registration/Deregistration\|De-registration Guide]].
			* Configuring your shell: [[.bashrc Do's and Don'ts]]

	<!--* If you need an SSH key for your workflow, read [[Registration/SSH\|Registering SSH Keys with your Cluster]].-->		<!--* If you need an SSH key for your workflow, read [[Registration/SSH\|Registering SSH Keys with your Cluster]].-->