Faq - Revision history

Tallada at 15:05, 15 April 2026

2026-04-15T15:05:17Z

Tallada at 14:09, 15 April 2026

2026-04-15T14:09:44Z

Tallada: /* What is the simplest way to avoid repeated SSH authentication? */

2026-04-15T13:57:45Z

What is the simplest way to avoid repeated SSH authentication?

Tallada: /* What is the simplest way to avoid repeated SSH authentication? */

2026-04-15T13:57:33Z

What is the simplest way to avoid repeated SSH authentication?

Tallada: /* What is the simplest way to avoid repeated SSH authentication? */

2026-04-15T13:57:07Z

What is the simplest way to avoid repeated SSH authentication?

Tallada at 13:55, 15 April 2026

2026-04-15T13:55:37Z

Tallada at 13:32, 15 April 2026

2026-04-15T13:32:08Z

Tallada at 13:24, 15 April 2026

2026-04-15T13:24:23Z

Eriksen at 13:44, 20 December 2025

2025-12-20T13:44:18Z

Eriksen at 21:02, 7 February 2025

2025-02-07T21:02:23Z

@@ Line 48: / Line 48: @@
 Afterwards, we recommend removing the old OTP factor from the [https://idp.pic.es/realms/PIC/account/account-security/signing-in user profile section].
-=== What is the simplest way to avoid repeated SSH authentication? ===
+== What is the simplest way to avoid repeated SSH authentication? ==
 The easiest way is to configure your SSH connection using '''ControlMaster''', which allows multiple sessions to reuse a single authenticated connection.

@@ Line 33: / Line 33: @@
 Follow these steps to recover your account and configure a new OTP token.
-# On the Keycloak login page, click '''Forgot password / OTP'''.
+# On the login page, click '''Forgot password / OTP''' or go [https://www.pic.es/reset here].
 # Enter your username. You should receive a recovery email in your inbox.
 # Open the email and follow the recovery link.

@@ Line 64: / Line 64: @@
 Host ui04.pic.es
 </pre>
 Initiate the first SSH connection and authenticate via the provided URL. You will see something like:

@@ Line 66: / Line 66: @@
-Initiate the first SSH connection and authenticate via the provided URL:
+Initiate the first SSH connection and authenticate via the provided URL. You will see something like:
 <pre>
 $ ssh ui04.pic.es
 (tallada@ui04.pic.es) Authenticate at https://idp.pic.es/realms/PIC/device?user_code=FPTB-HKEV and press ENTER.
 </pre>

@@ Line 51: / Line 51: @@
 The easiest way is to configure your SSH connection using '''ControlMaster''', which allows multiple sessions to reuse a single authenticated connection.
-<ol>
+On your client machine, edit the file <code>~/.ssh/config</code> and add the following lines:
 <pre>
 Host *
@@ Line 65: / Line 64: @@
 Host ui04.pic.es
 </pre>
-<li>Initiate the first SSH connection and authenticate via the provided URL:
 <pre>
@@ Line 80: / Line 79: @@
 Complete the authentication in your browser, then press ENTER.
-</li>
+Once authenticated, the SSH connection remains open in the background, and you can safely close your terminal session.
 The connection will persist indefinitely (until machine reboot or a network interruption).
-<li>Subsequent SSH connections to the same host will reuse the existing session and will not require authentication again:
+Subsequent SSH connections to the same host will reuse the existing session and will not require authentication again:
 <pre>
 $ ssh ui04.pic.es
 </pre>
 </li>
 </ol>

← Older revision		Revision as of 13:55, 15 April 2026
Line 47:		Line 47:

	Afterwards, we recommend removing the old OTP factor from the [https://idp.pic.es/realms/PIC/account/account-security/signing-in user profile section].		Afterwards, we recommend removing the old OTP factor from the [https://idp.pic.es/realms/PIC/account/account-security/signing-in user profile section].
		+
		+	=== What is the simplest way to avoid repeated SSH authentication? ===
		+	The easiest way is to configure your SSH connection using '''ControlMaster''', which allows multiple sessions to reuse a single authenticated connection.
		+
		+	<ol>
		+	<li>On your client machine, edit the file <code>~/.ssh/config</code> and add the following lines:
		+	<pre>
		+	Host *
		+	ControlMaster auto
		+	ControlPath ~/.ssh/cm-%r@%h:%p
		+	ControlPersist yes
		+	</pre>
		+
		+	Instead of <code>Host *</code>, you can restrict this to a specific host, for example:
		+
		+	<pre>
		+	Host ui04.pic.es
		+	</pre>
		+	</li>
		+
		+	<li>Initiate the first SSH connection and authenticate via the provided URL:
		+
		+	<pre>
		+	$ ssh ui04.pic.es
		+	</pre>
		+
		+	You will see something like:
		+
		+	<pre>
		+	(tallada@ui04.pic.es) Authenticate at https://idp.pic.es/realms/PIC/device?user_code=FPTB-HKEV and press ENTER.
		+	</pre>
		+
		+	Complete the authentication in your browser, then press ENTER.
		+	</li>
		+
		+	<li>Once authenticated, the SSH connection remains open in the background, and you can safely close your terminal session.
		+
		+	The connection will persist indefinitely (until machine reboot or a network interruption).
		+	</li>
		+
		+	<li>Subsequent SSH connections to the same host will reuse the existing session and will not require authentication again:
		+
		+	<pre>
		+	$ ssh ui04.pic.es
		+	</pre>
		+	</li>
		+	</ol>

← Older revision		Revision as of 13:32, 15 April 2026
Line 29:		Line 29:
	klist		klist
	</pre>		</pre>
		+
		+	== I lost access to my OTP, how can I reset it? ==
		+	Follow these steps to recover your account and configure a new OTP token.
		+
		+	# On the Keycloak login page, click '''Forgot password / OTP'''.
		+	# Enter your username. You should receive a recovery email in your inbox.
		+	# Open the email and follow the recovery link.
		+	# Scan the new QR code with your authenticator app.
		+	# Enter the generated OTP code and a device name.
		+	#* The device name is mandatory.
		+	# Change your password when prompted.
		+	#* This is required for security reasons.
		+	# Log in again as usual.
		+	#* On the OTP selection page, you will see two devices.
		+	#* Select the device with the name you just entered.
		+	#* The old one will usually appear as '''unnamed''' (if no name was set previously).
		+
		+	Afterwards, we recommend removing the old OTP factor from the [https://idp.pic.es/realms/PIC/account/account-security/signing-in user profile section].

← Older revision		Revision as of 13:24, 15 April 2026
Line 5:		Line 5:
	== Can an undergraduate student in my group have an account? ==		== Can an undergraduate student in my group have an account? ==
	Yes. Undergraduate students can have PIC accounts without any problem.		Yes. Undergraduate students can have PIC accounts without any problem.
		+
		+	== How do I get a Kerberos token? ==
		+	A valid token is needed to interface with some PIC services, like the Hadoop platform (HDFS, Hive, Spark, ...) or CTA.
		+	Tokens are issued for the machine in which they are requested, if you hop to another machine, you may need to get another token.
		+
		+	In order to get a token, run the following commands on a terminal.
		+	If you are on JupyterLab, use ''Launcher'' → ''Terminal''.
		+
		+	<pre>
		+	kinit -n -c ~/.fast.ccache @PIC.ES
		+	kinit -T ~/.fast.ccache
		+	</pre>
		+
		+	You could also define an alias for your own convenience:
		+
		+	<pre>
		+	alias kinit="kinit -n -c ~/.fast.ccache @PIC.ES; kinit -T ~/.fast.ccache"
		+	</pre>
		+
		+	Optionally, you can check the presence and expiration date of your token using:
		+
		+	<pre>
		+	klist
		+	</pre>

@@ Line 1: / Line 1: @@
-==How do I reset my password?==
+== How do I reset my password? ==
-You can reset the password [https://www.pic.es/user/auth/forgotpw here].
+You can reset your password using the following link:
-==Can an undergraduate student in my group have an account?==
+== Can an undergraduate student in my group have an account? ==
-Yes. No problem.
+Yes. Undergraduate students can have PIC accounts without any problem.

← Older revision		Revision as of 21:02, 7 February 2025
Line 1:		Line 1:
−	==How do I reset my password==	+	==How do I reset my password?==
	You can reset the password [https://www.pic.es/user/auth/forgotpw here].		You can reset the password [https://www.pic.es/user/auth/forgotpw here].
		+
		+	==Can an undergraduate student in my group have an account?==
		+	Yes. No problem.