Libraries tagged by dig

Single-sign on plugin for Pimcore. Supports OpenID and LDAP. SAML and OAuth2 coming soon

Go to Download

Add portlets to embed websites to Pimcore dashboards

Go to Download

Enables bundles for pimcore projects (replacement for bin/console pimcore:bundle:enable)

Go to Download

Composer require-dev dependencies for AZ Quickstart projects.

Go to Download

Supplementary Icon Set for the University of Arizona.

Go to Download

University of Arizona theme for Bootstrap.

Go to Download

Exception-based wrappers for json_encode and json_decode

Go to Download

A factory for constructing objects from arrays of properties

Go to Download

Relay support for digiaonline/graphql

Go to Download

A package to create e-wallets for managing and analysing digital financial assets per entity in your laravel application.

Go to Download

Encrypt numeric data (binary, decimal, hex) preserving it's format (eg. 16-digits card number to 16-digits encrypted number).

Go to Download

A SetaPDF-Signer component signature module for the GlobalSign Digital Signing Service.

Go to Download

Integrate pixx.io DAM Digital Asset Management into TYPO3. Use files from your pixx.io media pool with TYPO3 easily and without any detour. Use the search field to search through your pixx.io media library and find the right picture in a flash.

Go to Download

PHP Pagination Class with 4 types: Simple Pagination, Google Pagination, Digg/PHPBB Pagination Style.

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