How to Install and Uninstall perl-Mojo-JWT Package on openSUSE Leap
Last updated: December 24,2024
1. Install "perl-Mojo-JWT" package
In this section, we are going to explain the necessary steps to install perl-Mojo-JWT on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-Mojo-JWT
Copied
2. Uninstall "perl-Mojo-JWT" package
Here is a brief guide to show you how to uninstall perl-Mojo-JWT on openSUSE Leap:
$
sudo zypper remove
perl-Mojo-JWT
Copied
3. Information about the perl-Mojo-JWT package on openSUSE Leap
Information for package perl-Mojo-JWT:
--------------------------------------
Repository : Main Repository
Name : perl-Mojo-JWT
Version : 0.09-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 43.6 KiB
Installed : No
Status : not installed
Source package : perl-Mojo-JWT-0.09-bp155.1.4.src
Upstream URL : https://metacpan.org/release/Mojo-JWT
Summary : JSON Web Token the Mojo way
Description :
JSON Web Token is described in https://tools.ietf.org/html/rfc7519.
Mojo::JWT implements that standard with an API that should feel familiar to
Mojolicious users (though of course it is useful elsewhere). Indeed, JWT is
much like Mojolicious::Sessions except that the result is a url-safe text
string rather than a cookie.
In JWT, the primary payload is called the 'claims', and a few claims are
reserved, as seen in the IETF document. The header and the claims are
signed when stringified to guard against tampering. Note that while signed,
the data is not encrypted, so don't use it to send secrets over clear
channels.
--------------------------------------
Repository : Main Repository
Name : perl-Mojo-JWT
Version : 0.09-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 43.6 KiB
Installed : No
Status : not installed
Source package : perl-Mojo-JWT-0.09-bp155.1.4.src
Upstream URL : https://metacpan.org/release/Mojo-JWT
Summary : JSON Web Token the Mojo way
Description :
JSON Web Token is described in https://tools.ietf.org/html/rfc7519.
Mojo::JWT implements that standard with an API that should feel familiar to
Mojolicious users (though of course it is useful elsewhere). Indeed, JWT is
much like Mojolicious::Sessions except that the result is a url-safe text
string rather than a cookie.
In JWT, the primary payload is called the 'claims', and a few claims are
reserved, as seen in the IETF document. The header and the claims are
signed when stringified to guard against tampering. Note that while signed,
the data is not encrypted, so don't use it to send secrets over clear
channels.