shell app needs password when ssh the login node
in the shell access in clusters, the web ssh needs password to log in.

[xnip2021-06-24\_20-00-46]

but the [official video](https://www.osc.edu/resources/online_portals/ondemand) shows a non-password log in.

is needing password right? or what should i config to ssh without password.

thanks!

my related setting:

ondemand version 2.0

os version: centos …
hi and welcome!

it’s not an open ondemand thing. you need to setup sshd to allow for hostbasedauthentication and generate some key pairs. this setups some sort of trust between 2 or more servers saying “if you’ve logged into one of them, you can login to the other directly”.

of course we use lots…
sign in? as long as you are connected to the same network there is no need to sign in. you can download the sonos app, launch it, then choose "connect to an existing system". there are certain menus in the settings area that will require the username/password of the sonos account used to setup, but you can use all the other features right away. first of all, you need to check if you are using a self-signed certificate.

if so, you have to accept it first: double-clicked on the request in the network pane, and ow prompted you whether you wanted to accept the certificate.

other option will be to use the [overwolf.web.sendhttprequest()](http://developers.overwolf.com/documentation/sdk/overwolf/web/#sendhttprequest) funct… [@udo](/u/udo),

you should be verifying the token no matter what, which would require decoding it. if you are using our sdk then this is already happening.

the important distinction here is which token. are you talking about the id token or the access token? the permissions may be in the at, but the at is n… you could use on-demand tls with local certs if you don’t know ahead of time which ip the request will come from:

tls internal {

on\_demand

}

[image]

[tls (caddyfile directive) - caddy documentation](https://caddyserver.com/docs/caddyfile/directives/tls)

caddy is a powerful, enterprise-ready, open source web server with automatic https writ… From the official Node.js documentation:



> 
> A Node.js package is also available in the official repo for Debian Sid (unstable), Jessie (testing) and Wheezy (wheezy-backports) as “nodejs”. **It only installs a nodejs binary.**
> 
> 
> 


So, if you only type `sudo apt-get install nodejs` , it does not install other goodies such as **npm**. 


You need to type:



```
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
sudo apt-get install -y nodejs

```


> 
> Optional: install build tools
> 
> 
> To compile and install native add-ons from npm you may also need to install build tools:
> 
> 
> 



```
sudo apt-get install -y build-essential

```

More info: [Docs](https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions-enterprise-linux-fedora-and-snap-packages) see this link for account handling:https://support.sonos.com/s/article/3427?language=en\_usyou will find help for changing accounts, resetting passwords, etc. to access through [wd2go.com](http://wd2go.com) you need to setup remote access for these users in the nas admin. they will receive an email notification to create an account on [wd2go.com](http://wd2go.com). these credentials will be formed by their email address and a password for [wd2go.com](http://wd2go.com) that does not need to be the same one as whate… you have to forward the sip and rtp ports of the snom. (before the update this was done by a sip application layer gateway, but we had to remove this because it breaks security.)

[image]

[security announcement: mitigating nat slipstreaming - the ipfire blog](https://blog.ipfire.org/post/security-announcement-mitigating-nat-slipstreaming)

last autumn, we learned about … this is because the /login page, once a login occurs, the ‘state’ parameter is missing and so when the page tries to call the /authorize url it will error. the state parameter is used to mitigate csrf attack and so during authentication, the application sends this parameter in the authorization … [orafik](/members/orafik) thanks, unfortunately this is for an older version that i am not using. i actually found one 

<https://support.solarwinds.com/successcenter/s/article/setup-ssl-and-enable-smart-card-cac-pki-user-authentication-for-orion-web-console?language=en_us>