Download the PHP package psecio/jwt without Composer
On this page you can find all versions of the php package psecio/jwt. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package jwt
JWT (JSON Web Token) Creation and Decoding Library
This library allows for the creation and decoding of JWT (JSON Web Tokens).
Installation
This tool can be installed via Composer:
Example Usage
In the example below, the JWT object is created and a Header instance is assigned (required). The JWt object is then
assigned several claims: issuer, audience, issued at and not before to define data and how it could be processed. The encode
method is then called with the key and a resulting JWT-formatted string is returned.
NOTE: The JWT token will be generated in the order the claims are provided. No sorting is done in the background.
The decode method can then be called on the data along with the key to return an object matching the state of the jwt object.
Encryption via OpenSSL
The JWT Library also supports encryption of the resulting JWT-formatted string. Here's an example of it in use:
Custom Claim values
You can also add your own custom claim values to the JWT payload using the custom method. The first paramater is the value and the second is the claim "type" (key):
You can use any of the OpenSSL cypher methods provided by the openssl_get_cipher_methods on your system.
Supported Claim Types
- Audience (aud)
- Expire Time (exp)
- Issued At (iat)
- Issuer (iss)
- JwtId (jit)
- Not Before (nbf)
- Subject (sub)
- Private
Hashing types
By default this JWT tool uses HMAC hashing (HS256) to generate the signature for the request. There are other options for this that will use the OpenSSL functionality to let you use public and private keys for these methods:
- HS256
- HS384
- HS512
- ES256
- ES384
- ES512
- RS256
- RS384
- RS512
You cannot use a simple text string for the key like you can with HMAC hashing, so you must provide a valid key instance for the library to use. Here's an example using a .pem private key file and the RS256 hashing:
An exception (\Psecio\Jwt\Exception\InvalidKeyException) will be thrown if the key is invalid and cannot be used in signing the request. If there is an error during the actual signing of the message, you will be thrown a \Psecio\Jwt\Exception\SignatureErrorException.
