Libraries tagged by user id

model-tracks-user-updates is a library that updates the 'updated_by_user' column with the corresponding user id. Internally it uses the model triggers to update the column with the id of the logged user.

Go to Download

Scope for field 'user_id' (int)

Go to Download

ABRouter internal tool for handling related user's ids

Go to Download

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

Go to Download

This plugin allows users to switch between different accounts (and check for new mails) in a single Roundcube session.

Go to Download

Bypass login to test your application locally using users with different roles or by user id.

Go to Download

UserBase PHP Client: Identity + Login + Signup Service

Go to Download

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

Go to Download

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

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

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

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