Home/ Questions/Q 8231007
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T17:19:45+00:00

I’m going to implement OAuth 2.0 and REST API with it to grant different

  • 0

I’m going to implement OAuth 2.0 and REST API with it

to grant different permissions per users and also to scale well.

To scale well, stateless is easier because there is

NO file, database, in-memory based session with it.

Below is how I understand OAuth 2.

  1. OAuth Server give an access token to a user.
  2. The user’s access token is stored in cookie.
  3. When user access to REST API, user sends with the access token.
  4. Server receives request with access token.
  5. Server find out whether access token is valid and the user has permission to do request.
  6. Do or reject based on user’s privilege.

So I do not have to worry about session storage. Right?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What you are describing here, is the OAuth 2 Implicit Grant flow. OAuth 2 also includes three other flows, but as it seems that your ressource owner (the user) is initiating requests using browser side Javascript (you were talking about cookies), this is the flow you should go for.

    On client side, OAuth only requires you to store the access_token for accessing protected ressources (and a refresh_token if you’re going for an expiring access_token).

    • 0