Thanks Ward.
I did the following:
$ slurmrestd unix:/var/run/slurmrestd.socket -a rest_auth/local -s v0.0.36
-vvv
and to test the response:
$ curl --unix-socket /var/run/slurmrestd.socket
localhost/slurm/v0.0.36/ping (here "localhost" can be whatever
character, need to check --unix-socket curl option!)
$ echo -e "GET /slurm/v0.0.36/ping HTTP/1.1\r\n" | socat
unix-connect:/var/run/slurmrestd.socket STDIO
$ echo -e "GET /slurm/v0.0.36/ping HTTP/1.0\r\n" | nc -U
/var/run/slurmrestd.socket
All of them are working.
So in this case the only requirement for a user is having the read/write
permission on the socket?
My goal at the end would be to let a Dockerized client application
communicate with Slurmrestd server (running on the host). Guess I need to
mount the socket in the container but haven't tried yet.
Thanks,
Simone
****************************************************************
Simone Riggi, PhD
INAF, Osservatorio Astrofisico di Catania
Via S. Sofia 78
95123, Catania - Italy
phone: +39 095 7332 extension 282 (or 310)
e-mail: simone.ri...@gmail.com,
sri...@inaf.it <sri...@oact.inaf.it>,
sri...@pec.it <simone.ri...@ct.infn.it>
skype: simone.riggi
****************************************************************
On Fri, 9 Apr 2021 at 14:26, Ward Poelmans <ward.poelm...@vub.be> wrote:
> Hi Simone,
>
> On 8/04/2021 23:23, Simone Riggi wrote:
> > $ scontrol token lifespan=7200 username=riggi
> >
> > How can I configure and test the other auth method (local)? I am using
> > jwt at the moment.
> > I would like a user to be always authorized to use the rest API.
>
> local means socket (so you don't need a token). Start it with:
> slurmrestd unix:/var/run/slurmrestd.socket
>
> Ward
>
>
