← Passwords u sigurtà

Password / għodod tas-sigurtà

Dekoder JWT

Spezzjona header JWT, pretensjonijiet ta 'tagħbija u ħin lokalment, mingħajr verifika tal-firma.

Jiġi fil-browser tiegħek

Id-dejta dekodifikata mhix verifikata. Din l-għodda ma tivverifikax il-firma, l-emittent jew l-udjenza u m'għandhiex tintuża biex tivverifika token.

JWT bi tliet partijiet, sa 64 KiB. It-tokens JWE b'ħames partijiet kriptati mhumiex appoġġjati.

Header u payload huma dekodifikati lokalment bħala JSON. L-ebda token ma jintbagħat lil server jew maħżun minn din l-għodda. Ċara l-input meta tispiċċa, speċjalment fuq apparat kondiviż.

English guide · Ghid în română

Practical guide

Inspect the header and payload of a JSON Web Token while debugging a system you control. Decoding reveals claims but does not verify who issued them or whether the signature is valid.

Steps that matter

  1. Prefer a test token with no real personal data or active production permissions.
  2. Paste the complete token and inspect its header, payload and interpreted time claims.
  3. Perform signature, issuer, audience and policy validation in the receiving application before trusting any claim.

Worked example

An exp claim is a timestamp in seconds since the Unix epoch. A decoded token with a future exp can still have a forged signature, the wrong audience or revoked permissions.

Check before using the result

  • The decoder does not decrypt encrypted tokens or validate a token for authentication.
  • Treat tokens as credentials even if their payload looks harmless. Do not include them in bug-report emails or screenshots.