Helix/Login

1 Prerequisites for Login

• You have registered your account at the registration server for bwForCluster Helix.
  • If this is still missing, then please log in to https://bwservices.uni-heidelberg.de and click on "Register" in section "bwForCluster Helix".

• You have set a service password for bwForCluster Helix.
  • If you have not done so already, then please log in to https://bwservices.uni-heidelberg.de and select "Set Password" in section "bwForCluster Helix".

• You have set up a time-based one-time password (TOTP) for the two factor authentication (2FA) log in.
  • If this is still missing, then please follow the instructions for registering a new 2FA token on the following page: 'new-page-in-preparation'.

• Your IP is within the IP range of your university. Either you are working on a computer on your campus or you are connected via a virtual private network (VPN) to your university.
  • If you have an external IP (i.e. home office) and you are not connected via VPN to your university, you can not connect to bwForCluster Helix. Please consult the documentation of your university how to connect to your university via VPN.

2 Login to bwForCluster Helix

After registration bwForCluster Helix can be accessed via Secure Shell (SSH). Only SSH is allowed for login.

From Linux machines, you can log in using the following command:

ssh <UserID>@<login-server-to-be-named>

To run graphical applications, you need to enable X11 forwarding with the -X option:

ssh -X <UserID>@<login-server-to-be-named>

For SSH client programs with graphical user interfaces, fill in UserID and login server name accordingly. For Windows you can use PuTTY or MobaXterm. The later comes with an integrated X11 server which is necessary for the work with graphical applications.

The bwForCluster Helix has serveral login nodes. The selection of the login node is done automatically. If you log in multiple times, different sessions might run on different login nodes. In general, you should use the generic hostnames given above to allow us to balance the load over the login nodes.