federated_identity_login
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| federated_identity_login [2022/07/27 14:42] – pwolinsk | federated_identity_login [2025/10/15 19:51] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== Federated Identity with Globus ID ==== | ==== Federated Identity with Globus ID ==== | ||
| - | Globus ID ([[https:// | + | Globus ID ([[https:// |
| + | **NOTE:** To log into Pinnacle, both a Globus ID and an associated local Pinnacle account have to exist. | ||
| - | ==== Using Globus ID to log into AHPCC ==== | + | ==== Using a Globus ID to log into AHPCC ==== |
| - | **oauth-ssh** client is needed to authorized a host machine to connect to the AHPCC cluster using a Globus ID. The **oauth-ssh** is a python package that can be installed using pip: | + | **oauth-ssh** client is needed to authorized a host machine to connect to the AHPCC cluster using a Globus ID. The **oauth-ssh** is a python package that can be installed using **pip** (python package manager): |
| < | < | ||
| Line 30: | Line 31: | ||
| </ | </ | ||
| - | Once **oauth-ssh** client is installed, your client machine (the host from which your are logging into Pinnacle) has to be authorized to connect to Pinnacle login node, **login.hpc.uark.edu**: | + | Once **oauth-ssh** client is installed, your client machine (the host from which your are logging into Pinnacle) has to be authorized to connect to the Pinnacle login node, **login.hpc.uark.edu**: |
| < | < | ||
| Line 61: | Line 62: | ||
| < | < | ||
| - | pawel@frontdesk ~]$ oauth-ssh login.hpc.uark.edu | + | [pawel@frontdesk ~]$ oauth-ssh login.hpc.uark.edu |
| Last failed login: Wed Jul 27 08:14:45 CDT 2022 from 184.180.249.7 on ssh:notty | Last failed login: Wed Jul 27 08:14:45 CDT 2022 from 184.180.249.7 on ssh:notty | ||
federated_identity_login.1658932975.txt.gz · Last modified: (external edit)
