Libraries tagged by authenticate

Discover IMAP/SMTP settings, authenticate via any email

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

EAuth extension allows to authenticate users by the OpenID, OAuth 1.0 and OAuth 2.0 providers.

Go to Download

miniOrange SAML Single Sign on (SSO) plugin acts as a SAML Service Provider which can be configured to establish the trust between the plugin and a SAML capable Identity Providers to securely authenticate the user to the Laravel site. We support all known IdPs – ADFS, Azure AD, Google Apps, Okta, Salesforce, Shibboleth, SimpleSAMLphp, OpenAM, Centrify, Ping, RSA, IBM, Oracle, OneLogin, Bitium, WSO2, NetIQ etc.

Go to Download

Automatically logs-in users if they are already authenticated by a remote source. (e.g. environment variable REMOTE_USER)

Go to Download

An authentication driver for Laravel5 which allows to authenticate users using their legacy Django PBKDF2

Go to Download

jwt auth for encode decode and token expire_in authenticate

Go to Download

module for Jelix,allowing to authenticate with an ldap server and to register users locally.

Go to Download

Encrypt and authenticate PHP session data using AES-256 and HMAC-SHA256

Go to Download

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

Go to Download

Authenticates users through the Drupal one time login mechanism.

Go to Download

This package allows JWT-authenticated users to be stored and management in Redis with their roles, permissions, statuses and anything you want.

Go to Download

PHP 8+ Implementation of Ascon, a family of authenticated encryption (AEAD) and hashing algorithms designed to be lightweight.

Go to Download

Debugging a problem and need to login as one of your customers? This allows you to authenticate as any of your customers.

Go to Download

Authenticates users based on IP address settings

Go to Download