0

I have web client which invokes multiple services. As soon as the user is authenticated, I want to store the email Id somewhere as it sends the email Id for each request.

I don't want to use session as I have heard that is the best practice. In REST, all data must be sent for the request and it must be stateless. What other alternatives are there? Is using DB for session management still not breaking the stateless principle of REST?

I went through If REST applications are supposed to be stateless, how do you manage sessions? but there were many contradicting opinions there. Should the email Id be stored in session storage of the browser then?

codingsplash
  • 3,616
  • 6
  • 37
  • 76

1 Answers1

1

I think you should do it with a authentication header. Check out these threads:

Masterhead
  • 53
  • 6