Problems with WS client authentication.
Hi,
I'm trying to have a PI poll a GPS and send that to signal-k using WS. I'm running version 2.15.3 on Debian 11 bullseye. I create a read/write user, I use the signalk-generate-token command: signalk-generate-token -u pi2 -e 1y -s ~/.signalk/security.json. A token is generated, however it's not added to to security.json file. I've tried adding one manually then restarting the server, but authentication continues to fail.
Any idea what's going on here?
I assume there's a bug with 'generate-token', but to get it going manually do I need to add anything else in security.json beside what's here:
{
"username": "local-pi",
"type": "readwrite",
"password": "$2a$10$5JfSICCRvsjxnmUMtSkuJO9IhpXUMkhE.o790dWIUPpFC0K2J8juC",
"api-tokens": [
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImxvY2FsLXBpIiwiaWF0IjoxNzU3MDMwMDk0LCJleHAiOjE3ODg1ODc2OTR9.2j4NtNa-Duz8G6D-XBO5ptHjDou0hWlgCenE-EAW2Tw"
}
]
},
Thanks much!
I'm trying to have a PI poll a GPS and send that to signal-k using WS. I'm running version 2.15.3 on Debian 11 bullseye. I create a read/write user, I use the signalk-generate-token command: signalk-generate-token -u pi2 -e 1y -s ~/.signalk/security.json. A token is generated, however it's not added to to security.json file. I've tried adding one manually then restarting the server, but authentication continues to fail.
Any idea what's going on here?
I assume there's a bug with 'generate-token', but to get it going manually do I need to add anything else in security.json beside what's here:
{
"username": "local-pi",
"type": "readwrite",
"password": "$2a$10$5JfSICCRvsjxnmUMtSkuJO9IhpXUMkhE.o790dWIUPpFC0K2J8juC",
"api-tokens": [
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImxvY2FsLXBpIiwiaWF0IjoxNzU3MDMwMDk0LCJleHAiOjE3ODg1ODc2OTR9.2j4NtNa-Duz8G6D-XBO5ptHjDou0hWlgCenE-EAW2Tw"
}
]
},
Thanks much!
