Why can i easily decode auth0 id_token on jwt.io? -


okay, i'm developing angular 2 app. i've added auth0 authentication, me handles sessions insecurely. jwt token not encrypted , saved inside localstorage. claims visible anyone, can decoded , revealed. not mention, web storage isn't secure place.

i'm opting jwts because later want transform web app desktop app electron , cannot use cookie-sessions. users have additional information such roles, don't want in db on every request, that's why store them in jwt. makes sense encrypt data, auth0 doesn't seem provide function.

if claims roles stored in localstorage unprotected, what's stopping me go firefox console , change token, e.g. make myself admin?

if claims roles stored in localstorage unprotected, what's stopping me go firefox console , change token, e.g. make myself admin?

because jwt signed, so alteration content or signature detected during validation

the digital signature, third part of jwt token hhhhhh.ppppppp.ssssss created using server private key, , way can verify identity of issuer of token , has not been altered

if want hide payload, jwt specification allows use encryption (see json web encryption-jwe @ rfc). if auth0 not support it, have lot of libraries listed in jwt.io


Comments

Popular posts from this blog

java - Suppress Jboss version details from HTTP error response -

gridview - Yii2 DataPorivider $totalSum for a column -

Sass watch command compiles .scss files before full sftp upload -