<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>jwt on GoScrapy Blog</title><link>http://goscrapy.com.ar/tags/jwt/</link><description>Recent content in jwt on GoScrapy Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>jackgris2@gmail.com (Gabriel Pozo)</managingEditor><webMaster>jackgris2@gmail.com (Gabriel Pozo)</webMaster><lastBuildDate>Wed, 10 May 2023 23:05:55 -0300</lastBuildDate><atom:link href="http://goscrapy.com.ar/tags/jwt/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an Authorization Service With Fiber Using JWT</title><link>http://goscrapy.com.ar/post/building-an-authorization-service-with-fiber-using-jwt/</link><pubDate>Wed, 10 May 2023 23:05:55 -0300</pubDate><author>jackgris2@gmail.com (Gabriel Pozo)</author><guid>http://goscrapy.com.ar/post/building-an-authorization-service-with-fiber-using-jwt/</guid><description>What is JWT? JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.
Although JWTs can be encrypted to provide secrecy between parties, we will focus on signed tokens.</description></item></channel></rss>