JWT and server side token storage -


every article i've read vouching advantages of jwt state 1 of these advantages ability auth system distributed across multiple servers. i.e . aren't relying on central repository of user auth details lookup on every request.

however when comes implementation, i've read in many places added security shouldn't rely on jwt signature verification itself, , should maintain list of black or white list tokens generated server.

doesn't defeat advantage i've listed above, list of tokens need stored centrally servers can access , require lookup on each request?

how have people implemented on end?

you making points in question. make sense store oauth token @ central location in order make easier implement signout/revoke functionality. if relied on token signature couldn't have possibly implemented such feature. suppose user wanted revoke access token. in case if didn't have central location/datastore tokens have invalidated , relied on token signature, token still have been valid.

so indeed, when want build more advanced systems dependent on oauth tokens, central store tokens more must.


Comments

Popular posts from this blog

how to insert data php javascript mysql with multiple array session 2 -

multithreading - Exception in Application constructor -

windows - CertCreateCertificateContext returns CRYPT_E_ASN1_BADTAG / 8009310b -