Login Problems: Difference between revisions
K Siegmund (talk | contribs) (Created page with "This page lists common causes for problems with logging in as well as listing information you should provide when writing a ticket == Missing Entitlement == This can happen because * you have not completed <b>User Access Step A</b> for a bwForCluster or bwUniCluster respectively * you have left University * there is a malfunction of the IDM of your University You can check your En...") |
K Siegmund (talk | contribs) No edit summary |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
This page lists common causes for problems with logging in as well as listing information you should provide when writing a ticket |
This page lists common causes for problems with logging in as well as listing information you should provide when writing a ticket |
||
== Things to Check First == |
|||
* Double-check your [[Registration/Login/Username|username]] and [[Registration/Password|password]]. |
|||
* Make sure your CAPS LOCK key is not enabled. |
|||
* Ensure your [[Registration/Account|account]] is not locked or expired. |
|||
* Try logging in from a different device or browser. |
|||
== Cannot Connect to Cluster at All == |
|||
Please note that you need to come from internet hosts inside your university network (Universities in Baden-Württemberg, BELWÜ). Either by connecting from a machine located on the campus or by using a VPN to virtually become part of the university network. Also note, that unauthenticated wireless connection options of a university may be considerd as out-of-network. |
|||
* Please check the information from the "Help Desk" tab on the website: https://wieistmeineip.scc.kit.edu/index.html.en_US or the ipv4 and ipv6 info from https://test-ipv6.com/. |
|||
== Missing Entitlement == |
== Missing Entitlement == |
||
| Line 6: | Line 18: | ||
This can happen because |
This can happen because |
||
* you have not completed <b>User Access Step A</b> for |
* you have not completed <b>User Access Step A</b> for the cluster you want to use: <br> → [[Registration/bwForCluster/Entitlement|bwForCluster]] or <br> → [[Registration/bwUniCluster/Entitlement|bwUniCluster]] |
||
* you have left University |
* you have left University |
||
* there is a malfunction of the IDM of your University |
* there is a malfunction of the IDM of your University |
||
| Line 14: | Line 26: | ||
→ <b>[[Registration/bwForCluster/Entitlement#Check_your_Entitlements|Check your Entitlements]]</b> |
→ <b>[[Registration/bwForCluster/Entitlement#Check_your_Entitlements|Check your Entitlements]]</b> |
||
In short: go to https://login.bwidm.de/ and select Index(Übersicht) → Personal Data, then select the tab "Shibboleth" and search for Cluster on that page to find <pre>http://bwidm.de/entitlement/bwUniCluster</pre> or <pre>http://bwidm.de/entitlement/bwForCluster</pre> (these are the names of the Entitlement, not links). |
|||
| ⚫ | |||
| ⚫ | |||
=== Missing bw Group === |
|||
You can also check if your compute project group still exists by selecting the tab "Groups" on the same page as described above. |
|||
== Lost TOTP Secret == |
== Lost TOTP Secret == |
||
| Line 23: | Line 41: | ||
→ see <b> [[Registration/2FA#Token_Management]] </b> |
→ see <b> [[Registration/2FA#Token_Management]] </b> |
||
Please contact us via authenticated login in the [[bwSupportPortal|Support Portal]] and not via Email. |
|||
We will only be able to deactivate your current secret, which will enable you to create a new one without having to enter a TOTP. |
|||
For the next steps, follow the relevant wiki page: https://wiki.bwhpc.de/e/Registration/2FA |
|||
In short: |
|||
a) Delete the old token, reload the web page and verify that all tokens have been deleted. |
|||
b) Create a new smartphone token and test it (if the QR code is missing check your browser's add-ons/ad-blockers) |
|||
c) Create a backup Tan List, print it on paper and keep in a safe place for cases like this |
|||
Note: Users from KIT Karlsruhe who are using a cluster which uses https://login.bwidm.de/ to register the service will need to contact KIT support to have the TOTP reset |
|||
== TOTP Secret Disabled == |
|||
After a certain number of unsuccessful TOTP attempts, your TOTP will have accumulated too many errors if no successful login resets this. |
|||
In this case, you will have to open a ticket at the [[bwSupportPortal|Support Portal]] for us to re-enable the TOTP. |
|||
Some programs used to open a ssh connection with some configuration options cause the client to keep trying to re-login in the background but fails because this mechanism cannot account for entering a TOTP. Please check configuration of your software for such behavior. |
|||
== Forgot Password == |
== Forgot Password == |
||
| Line 29: | Line 69: | ||
→ list or registration servers also at: <b> [[Registration/2FA#Token_Management]] </b> |
→ list or registration servers also at: <b> [[Registration/2FA#Token_Management]] </b> |
||
→ [[Registration/Password|How to reset your password]] |
|||
== ZAS Permission Missing (bwForClusters only) == |
== ZAS Permission Missing (bwForClusters only) == |
||
| Line 40: | Line 80: | ||
* There is a ZAS malfunction |
* There is a ZAS malfunction |
||
You can see the status of your own compute project or a project membership at |
You can see the status of your own compute project or a project membership at https://zas.bwhpc.de/en/zas_info_bwforcluster.php via the points "RV collaboration" or "My RVs". |
||
→ see <b> [[Registration/bwForCluster/RV|Rechenvorhaben/project]] </b> |
|||
== Writing a Ticket == |
== Writing a Ticket == |
||
Before writing a ticket to the [[Support Portal]], please check if your Entitlement is missing - in which case you should contact your own university support. |
Before writing a ticket to the [[bwSupportPortal|Support Portal]], please check if your Entitlement is missing - in which case you should contact your own university support. |
||
Please provide the following information: |
Please provide the following information: |
||
| Line 51: | Line 93: | ||
* your username |
* your username |
||
* your eppn |
* your eppn |
||
* ipv4 and ipv6 info from https://test-ipv6.com/ if you cannot connect at all |
|||
* The output of <code>ssh [[Registration/Login/Username|username]]@[[Registration/Login/Hostname|hostname]] -vvv</code> |
|||
Latest revision as of 17:01, 21 November 2025
This page lists common causes for problems with logging in as well as listing information you should provide when writing a ticket
Things to Check First
- Double-check your username and password.
- Make sure your CAPS LOCK key is not enabled.
- Ensure your account is not locked or expired.
- Try logging in from a different device or browser.
Cannot Connect to Cluster at All
Please note that you need to come from internet hosts inside your university network (Universities in Baden-Württemberg, BELWÜ). Either by connecting from a machine located on the campus or by using a VPN to virtually become part of the university network. Also note, that unauthenticated wireless connection options of a university may be considerd as out-of-network.
- Please check the information from the "Help Desk" tab on the website: https://wieistmeineip.scc.kit.edu/index.html.en_US or the ipv4 and ipv6 info from https://test-ipv6.com/.
Missing Entitlement
This can happen because
- you have not completed User Access Step A for the cluster you want to use:
→ bwForCluster or
→ bwUniCluster - you have left University
- there is a malfunction of the IDM of your University
You can check your Entitlements as shown on the Entitlement page:
In short: go to https://login.bwidm.de/ and select Index(Übersicht) → Personal Data, then select the tab "Shibboleth" and search for Cluster on that page to find
http://bwidm.de/entitlement/bwUniCluster
or
http://bwidm.de/entitlement/bwForCluster
(these are the names of the Entitlement, not links).
In case your Entitlement is missing, please contact the support of the university you are a member of. The bw Clusters rely on your university to provide the correct information about your ongoing affiliation and cannot solve the problem.
Missing bw Group
You can also check if your compute project group still exists by selecting the tab "Groups" on the same page as described above.
Lost TOTP Secret
Please avoid this problem by creating a backup TAN list and keep it in a safe place - e.g. in printed form in a folder in your office.
To create a backup tan list, use the registration server used by your cluster. You will be asked a current TOTP password from your device.
→ see Registration/2FA#Token_Management
Please contact us via authenticated login in the Support Portal and not via Email.
We will only be able to deactivate your current secret, which will enable you to create a new one without having to enter a TOTP.
For the next steps, follow the relevant wiki page: https://wiki.bwhpc.de/e/Registration/2FA
In short:
a) Delete the old token, reload the web page and verify that all tokens have been deleted. b) Create a new smartphone token and test it (if the QR code is missing check your browser's add-ons/ad-blockers) c) Create a backup Tan List, print it on paper and keep in a safe place for cases like this
Note: Users from KIT Karlsruhe who are using a cluster which uses https://login.bwidm.de/ to register the service will need to contact KIT support to have the TOTP reset
TOTP Secret Disabled
After a certain number of unsuccessful TOTP attempts, your TOTP will have accumulated too many errors if no successful login resets this.
In this case, you will have to open a ticket at the Support Portal for us to re-enable the TOTP.
Some programs used to open a ssh connection with some configuration options cause the client to keep trying to re-login in the background but fails because this mechanism cannot account for entering a TOTP. Please check configuration of your software for such behavior.
Forgot Password
You can re-set the ssh password on the registration server used by your cluster
→ list or registration servers also at: Registration/2FA#Token_Management → How to reset your password
ZAS Permission Missing (bwForClusters only)
This can have one of the following reasons:
- You have not yet successfully become a member of your compute project group
- Your account has been disabled by an RV owner or manager and no longer belongs to the compute project
- The compute project you are a member of has not been renewed and has expired
- There is a ZAS malfunction
You can see the status of your own compute project or a project membership at https://zas.bwhpc.de/en/zas_info_bwforcluster.php via the points "RV collaboration" or "My RVs".
→ see Rechenvorhaben/project
Writing a Ticket
Before writing a ticket to the Support Portal, please check if your Entitlement is missing - in which case you should contact your own university support.
Please provide the following information:
- which cluster you have tried to access
- your username
- your eppn
- ipv4 and ipv6 info from https://test-ipv6.com/ if you cannot connect at all
- The output of
ssh username@hostname -vvv