softwareengineering

What type of authentication/identification is needed?

The specs: Mobile apps LLM wrapper (of e.g. OpenAI API) The chat history will be stored on the client Backend is needed to manage the api key and to track token consumption / payment (how many tokens does the user/device have left?) Because we need to track the token consumption, we need some sort of identifier: Device UUID (generated in the client): easy, but seems unsafe User account (e.g. authentication with JWT token) Others (?) I have been working on the JWT authentication and I'm mostly done, so "more work" would not be a contra anymore. I just took a step back and wondered if it's not overkill for this situation. If it increases the security of the tokens/payments tracking, it seems worth it. Any suggestions?

Jun 9, 2025 - 02:10
 0

The specs:

  • Mobile apps
  • LLM wrapper (of e.g. OpenAI API)
  • The chat history will be stored on the client
  • Backend is needed to manage the api key and to track token consumption / payment (how many tokens does the user/device have left?)

Because we need to track the token consumption, we need some sort of identifier:

  • Device UUID (generated in the client): easy, but seems unsafe
  • User account (e.g. authentication with JWT token)
  • Others (?)

I have been working on the JWT authentication and I'm mostly done, so "more work" would not be a contra anymore. I just took a step back and wondered if it's not overkill for this situation. If it increases the security of the tokens/payments tracking, it seems worth it. Any suggestions?

Read More

Tags:

Previous Article

Best practice when working with code that uses current date and time

Next Article

Rawkode's Hands-on Intro to Fermyon Wasm Functions

Related Posts

What are some of the differences between the way C++ im...

Jun 3, 2025  0

When does encapsulating a primitive field into its own ...

May 22, 2025  0

Is there an equivalent to Actions on Google for Gemini?

May 25, 2025  0