Libraries tagged by user id

A bundle to easily manage your trackers and the consentement of your users to fit the RGPD standard

Go to Download

Allows backend users to select stock pictures from various online services

Go to Download

A Laravel Eloquent Model trait for adding User Id's to Eloquent Models

Go to Download

A library that provides remote user identification from oauth2 access tokens.

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

Envbar allows you to differentiate between environments by adding a custom colored bar above the top navigation. This should help backend users to identify the environment ( e.g local, develop, staging, production ) and prevent anyone from accidentally changing content on the wrong environment.

Go to Download

Create a GMail esque avatar based on the users intials & a persistant identifier such as an email address.

Go to Download

The purpose of the Authentication component is to provide support for different means of identification and authentication of users using different providers and protocols.

Go to Download

Share link http://{yourdomain}/dpa/add/tocart/sku/{product_sku}, http://{yourdomain}/dpa/add/tocart/sku/{product_sku}/coupon/{coupon_code}, http://{yourdomain}/dpa/add/tocart/sku/{product_sku}-{quantity}, http://{yourdomain}/dpa/add/tocart/sku/{product_sku_1},{product_sku_2}, http://{yourdomain}/dpa/add/tocart/id/{product_sku_1}-{quantity},{product_sku_2}-{quantity}, http://{yourdomain}/dpa/add/tocart/id/{product_id}, http://{yourdomain}/dpa/add/tocart/id/{product_id}-{quantity}, http://{yourdomain}/dpa/add/tocart/id/{product_id_1},{product_id_2} OR http://{yourdomain}/dpa/add/tocart/id/{product_id_1}-{quantity},{product_id_2}-{quantity} with your users through email, share media, blogs etc. Once user clicks on this link product will be automatically added to cart and user will be redirected to checkout page.

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

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download

Laravel wso2 identity api user is a Laravel Package for WSO2 IDP user

Go to Download

User module for AsgardCMS. Handles the authentication and authorisation as well as the user management.

Go to Download

This package allows you to take the identity of another user without entering the password. Keep in mind that you have to be very careful who we give access to this option, as it is ideal for admin users.

Go to Download

A Laravel 5 Package Provider to Identify/detect a user's browser, device, operating system and Language

Go to Download