Currently clients.json stores entries like:
{
"bot_id": 1234,
"bot_site": "...",
"created_at": "2024-02-12T10:08:04.477772",
"created_by": "...",
"proposal_id": 1234,
"proposal_no": 1234,
"stream": "some-pattern-1234",
"token": "............."
},On request, if the provided token matches one in the list of clients, that is used.
This was a quick and easy way to do things at the start and made it easy to modify what the tokens were allowed to do, but is a bit annoying now due to keeping this file around and migrating it on changes.
Service could instead issue its own JWT(S?)s containing the required information.
Currently
clients.jsonstores entries like:{ "bot_id": 1234, "bot_site": "...", "created_at": "2024-02-12T10:08:04.477772", "created_by": "...", "proposal_id": 1234, "proposal_no": 1234, "stream": "some-pattern-1234", "token": "............." },On request, if the provided token matches one in the list of clients, that is used.
This was a quick and easy way to do things at the start and made it easy to modify what the tokens were allowed to do, but is a bit annoying now due to keeping this file around and migrating it on changes.
Service could instead issue its own JWT(S?)s containing the required information.