Libraries tagged by pass
ammardev/laravel-wp-hash-driver
9121 Downloads
Supports Wordpress passwords hashing and checking in Laravel's Hash facade.
wufeifei/grw
6 Downloads
个人事务管理系统
ozh/phpass
69204 Downloads
Portable PHP password hashing framework
magiclabs/magic-laravel
6684 Downloads
Magic Admin Laravel Library
passioneight/php-utilities
4670 Downloads
passcreator/entitylog
46718 Downloads
ublaboo/simple-http-auth
13488 Downloads
Extension for Nette Framework: set user, password and presenters names to secure and they will be secured via simple http authentification
typo3/cms-saltedpasswords
320235 Downloads
Uses a password hashing framework for storing passwords. Integrates into the system extension "felogin". Use SSL or rsaauth to secure datatransfer! Please read the manual first!
toddish/verify
20686 Downloads
A simple authentication bundle for Laravel 4/5. It features roles, permissions, password salting and is fully extendable.
snmp-persist/snmp-persist
55148 Downloads
The SNMP pass_persist threaded backend
rullzer/easytotp
35511 Downloads
Time-Based One-Time Password according to RFC6238
rolfhaug/laravel-magic-link
7367 Downloads
Create magic login links to let users log in to any route with a URL (without password)
phpbb/epv
140581 Downloads
A extension validator for phpBB extensions. Extensions are required to pass the validator when submitted to the extension database.
paypaplane/svix-client
15084 Downloads
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.
ozanhazer/php-htpasswd
7377 Downloads
A lightweight - single class - library to read and write htpasswd. You can add or delete users or you can update their passwords...