@rp_st & @nkshah2 Hey We are using SuperToken React Native 3.2.0, So recently we are working on One of ther functionality where only single session should be valid on server per user. So when try to revoke all the session from SuperToken dashboard, we could see the session in multiple still valid. We even try to debug in SuperToken react native lib AXIOS.js file so we could see that session is still valid. So we are wondering what exactly are we doing wrong here. Can you please help us?

Hey. The access token is stateless. Therefore, they will be revoked from the frontend when it attempts a refresh.

@rp_st & @nkshah2 Hi, Thanks for quick revert. Just wanted to understand as you said access token is Stateless, so that the frontend still return as a valid session. However, when we call an API our backend calls verify session and still that returns as a valid sessions. Ideally there are no active sessions, so it should not return as a valid sessions. Can you please help us to understand this.

Hey @nilesh_97911 So since the access token is stateless it can be verified without calling the core. So a valid access token would still get verified normally after the session is revoked, it would fail the next time the session is refreshed (which would happen after the access token expires).