Skip to main content

RESTful API with session tokens.. ehh? [Resolved]

After looking at a lot of session/state debates with regard to REST and finding nothing concrete, I'm just going to cut to the chase and ask myself.

Developing a RESTful API as a backend for a mobile app, I (think I) want to keep track of all users (even unregistered ones) with guest sessions. This allows me to customise content and do statistics on my users.

Implementation-wise I would have my app identify itself, as if to an /authenticate end-point, just without e-mail/password, more like UUID. But this effectively makes my whole API expect a "session token" with each request.

Is this a bad approach, or would you do the same?


Asked January 11, 2017
Posted Under: Programming
46 views
2 Answers

The usual approach is to simply provide a session token back to the client via headers or cookies if they failed to provide one, or provided an invalid one. This is especially necessary for web clients where the session can time out while they're on a page somewhere. This ensures you have your session immediately, without going to the "authenticate" end-point, which should do what its name suggests: Authenticate the user.

Of course, this means that the client must be designed to expect the session token to change, but that's a good thing. Regenerating the session token, particularly on changes of privilege (ie, going from guest to full user), helps to prevent session hijacking. And don't think that just because you're a mobile app instead of a web page you're safe from hijacking. You're not, a hacker can use Fiddler or some other proxy to intercept your mobile API.


Answered January 11, 2017
 
Good input, thanks. – Zoon 2 days ago
 CanDoerz  9 months ago

Why this approach seems not a good idea ?

  1. Security reasons: Building your own "session token" comes with high risks of vulnerability. One example that come to my mind here is token hijacking (for example on the device, even if communication channel would be TLS protected).

  2. Anyway, conceptually, this doesn't fit in the architecture: your token will contain a unique number that you need to track on the side of the service. This means that the service has a state (e.g.active UUID). But in your question you want RESTful service, which means stateless.

  3. Alternatively you could avoid the state on the server by storing it in the token (i.e., the UUID, an additional information that combine with the UUID allows to assess that the UUID is valid, and the user id). But then, you expose yourself to the forgery of your token (e.g. login to get a proper UUID + then overwrite the user id with an id having more privilege).

Better alternative

In order to avoid making implementing a nest of vulnerabilities, use only proven standardized protocols. For example, instead of reinventing your own token, use proven JWT which is cryptographically secured.

Additional reading:


Answered January 11, 2017
 
Thanks for the feedback. I agree that using the well-established JWT for the token technology is the best approach, I was primarily thinking about state-fulness of the API if using a token with every request. – Zoon yesterday
 CanDoerz  9 months ago
Your Answer
D:\Adnan\Candoerz\CandoProject\vQA