Libraries tagged by jwt

A simple library to decode and parse Apple Sign In client tokens.

Go to Download

This library verifies that the signature of the JWT is valid, comes from a desired application, and that the token has not been tampered with or expired.

Go to Download

JWT, JWS and JWE implementation in PHP

Go to Download

Symfony SDK for Auth0 Authentication and Management APIs.

Go to Download

EU Login API Authentication Bundle, authenticate requests from European Commission corporate service 'EU Login' using OpenID Connect protocol.

Go to Download

A token manager for jwt tokens

Go to Download

JWT, JWS and JWS implementation in PHP

Go to Download

JWT, JWS and JWE implementation in PHP

Go to Download

Sample application demonstrating how to integrate Auth0 with Laravel 9 or Laravel 10 for session-based authentication and token-based authorization.

Go to Download

Symfony2 Jose Bundle

Go to Download

Simple Slim Framework 4 skeleton with Twig, Monolog, Doctrine in Sqlite.

Go to Download

Verify JWTs from AWS Cognito

Go to Download

PHP client for Apple Push Notification Service (APNs) - Send push notifications to iOS using the new APNs HTTP/2 protocol with token-based (JWT with p8 private key) or certificate-based authentication

Go to Download

# Introduction Welcome to the Passbase Verifications API docs. This documentation will help you understand our models and the Verification API with its endpoints. Based on this you can build your own system (i.e. verification) and hook it up to Passbase. In case of feedback or questions you can reach us under this email address: [[email protected]](mailto:[email protected]). A User submits a video selfie and valid identifying __Resources__ during a __Verification__ guided by the Passbase client-side integration. Once all the necessary __Resources__ are submitted, __Data points__ are extracted, digitized, and authenticated. These Data points then becomes part of the User's __Identity__. The User then consents to share __Resources__ and/or __Data points__ from their Identity with you. This information is passed to you and can be used to make decisions about a User (e.g. activate account). This table below explains our terminology further. | Term | Description | |-----------------------------------------|-------------| | [Identity](#tag/identity_model) | A set of Data points and Resources related to and owned by one single User. This data can be accessed by you through a Verification. | | Data points | Any data about a User extracted from a Resource (E.g. Passport Number, or Age). | | [Resource](#tag/resource_model) | A source document used to generate the Data points for a User (E.g. Passport). | | [User](#tag/user_model) | The owner of an email address associated with an Identity. | | Verification | A transaction through which a User consents to share Data points with you. If the Data points you request are not already available in the User's Identity, the Passbase client will ask the User to submit the necessary Resource required to extract them. | | Re-authentication (login) | A transaction through which a User can certify the ownership of Personal data previously shared through an Authentication. | # Authentication There are two forms of authentication for the API: • API Key • Bearer JWT Token

Go to Download

Package for validating a JWT token and checking the contained scopes

Go to Download