hey guys, I'm having a problem with token generati...
# server-apio
orange-dog-39581
10/01/2025, 5:09 PMhey guys, I'm having a problem with token generation. I wrote the system myself in Swift to connect via live kit's server api. I've double and triple checked our api key and secret but I'm still getting a bad primitive message when I try and start a room instance. This is going from a client side web socket connection through a backend in vapor that connects directly to livekit.
r
refined-appointment-81829
10/01/2025, 5:13 PMCan I see a token you generated
o
orange-dog-39581
10/01/2025, 5:15 PMsure, let me have the console log one. In the meantime this is the journalctl log snippet showing the error:
r
refined-appointment-81829
10/01/2025, 5:21 PMAlso, is the clock on your device correct?
o
orange-dog-39581
10/01/2025, 5:21 PMgoing to take just a few minutes, this is just a test backend instance so it takes like 10 minutes to rebuild but I just set it up to log the token output fro the generation method.
orange-dog-39581
10/01/2025, 5:22 PMThat's from last night, but, no. I believe 6 maps to 10pm central time
orange-dog-39581
10/01/2025, 5:22 PMsorry, 5.
r
refined-appointment-81829
10/01/2025, 5:22 PMOne common cause of that 401 error is a system clock that is not correct
o
orange-dog-39581
10/01/2025, 5:23 PMoh it's using the time in the seed?
r
refined-appointment-81829
10/01/2025, 5:23 PMthe token has a validity time frame. If you issue a token and the clock is not correct the validity range can fails when checked on the sever
o
orange-dog-39581
10/01/2025, 5:24 PMoh, ok. when this rebuild finishes, I'll attempt to connect just to get you a token output but then I'll change the system clock on the vm and see if that changes anything.
r
refined-appointment-81829
10/01/2025, 5:25 PMYou can decode the token here once you have it:
http://yepher.com/livekit/validate_token.html
o
orange-dog-39581
10/01/2025, 5:25 PMI hadn't done it because this is just the prototype backend so it's been quick and dirty in a lot of respects.
r
refined-appointment-81829
10/01/2025, 5:25 PMI am on a flight that will be landing soon so may have to drop soon.
o
orange-dog-39581
10/01/2025, 5:25 PMok, no worries. I'll keep working on it and if you disappear I'll know why.
orange-dog-39581
10/01/2025, 5:41 PMSo it comes back invalid via the yepher tool. using jwt.io I get valid token but invalid signature. Here's the token in question:
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJBUElqajJhY0VBNU1QNnEiLCJleHAiOjE3NTkzNDA5OTUsImlhdCI6MTc1OTM0MDM5NSwic3ViIjoiQVBJamoyYWNFQTVNUDZxIiwidmlkZW8iOnsicm9vbUNyZWF0ZSI6dHJ1ZSwicm9vbVJlY29yZCI6dHJ1ZSwicm9vbUxpc3QiOnRydWUsInJvb21BZG1pbiI6dHJ1ZX19.ZXrqflq2HtPELpntx8_vPTML-6eEUp5VEEZcFSSGHl0
orange-dog-39581
10/01/2025, 5:44 PMin the claims validator on jwt.io I get the correct API key in the iss and sub fields.
orange-dog-39581
10/01/2025, 7:36 PMI found the issue. was missing one character from the secret in my environment file so the length was under 256b making it an invalid signature. Literally one character.