Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
nigelm
3 years agoNew Contributor
Background ssh requests - Codinn Core Tunnel
I use Codinn's https://codinn.com/tunnel/ to manage ssh tunnels.
Starting recently (April 2023), when I start a tunnel up (click on menu app entry), rather than getting a 1Password ssh authorizati...
Former Member
2 years agoI am using the script command extension where I use my own custom bash script.
The script I have created looks like this:
```
!/bin/bash
Required parameters:
@raycast.schemaVersion 1
@raycast.title
@raycast.mode fullOutput
Optional parameters:
@raycast.icon ...
@raycast.argument1 { "type": "text", "placeholder": "Hostname" }
@raycast.argument2 { "type": "text", "placeholder": "Username" }
Setting TERM variable defines the terminal type. In other words, it sets the terminal type for which output is to be prepared.
For the SSH command, the options -ttyq are used to get connected as fast as possible and -q removes the connection closed message.
TERM=xterm-256color ssh -ttYq user@hostname "command on remote host with arguments $1 and $2"
```
My .ssh/config looks like this with a link to agent.sock:
```
1Password integration
Host *
IdentityAgent "~/.1password/agent.sock"
```
When I run the script from the terminal while 1Password is locked, I get prompted for authorisation from 1Password. After I have authorised it works to run both from the terminal and from Raycast.
When I run the script from Raycast while 1Password is locked, it just shows this icon in the toolbar and I have to click on "SSH request waiting" and then authorise the request: