38,760
edits
Automation in the context of multifactor authentication/en: Difference between revisions
Automation in the context of multifactor authentication/en (view source)
Revision as of 22:48, 1 March 2024
, 8 months agoUpdating to match new version of source page
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 43: | Line 43: | ||
Here is the hostname of the node to be used for unattended connections on each cluster: | Here is the hostname of the node to be used for unattended connections on each cluster: | ||
* Cedar: robot.cedar.alliancecan.ca | * Cedar: robot.cedar.alliancecan.ca | ||
* Graham: | * Graham: robot.graham.alliancecan.ca | ||
* Béluga: not available yet | * Béluga: not available yet | ||
* Narval: not available yet | * Narval: not available yet | ||
| Line 57: | Line 57: | ||
With <code>rsync</code>: | With <code>rsync</code>: | ||
{{Command|rsync -e "ssh -i .ssh/private_key_to_use" ...}} | {{Command|rsync -e "ssh -i .ssh/private_key_to_use" ...}} | ||
It's often much more convenient to put these parameters into your ~/.ssh/config file, so it gets picked up by any ssh client invocation. For instance: | |||
host robot | |||
hostname robot.cluster.alliancecan.ca | |||
user myrobot | |||
identityfile ~/.ssh/my-robot-key | |||
identitiesonly yes | |||
requesttty no | |||
this means that the following kinds of commands will do what you want: | |||
{{Command|ssh robot /usr/bin/ls}} | |||
{{Command|rsync -a datadir/a robot:scratch/testdata}} | |||