Libraries tagged by user verification
rinvex/fort
3722 Downloads
Rinvex Auth is a powerful authentication, authorization and verification package built on top of Laravel. It provides developers with Role Based Access Control, TwoFactor Authentication, Social Authentication, compatible with Laravelβs standard API and fully featured all-in-one solution out of the box.
atellitech/auth-hyperf
232 Downloads
Auth module for Hyperf supporting SSO JWT verification and user synchronization.
helsingborg-stad/active-directory-api-wp-integration
19638 Downloads
Simple plugin for verification of existing WordPress users with api.
rasulian/laravel-user-verification
39 Downloads
A package for user email and phone number verification with activation code
ahmedash95/users-verification
21 Downloads
Laravel Package for managing users verification.
chapdel/verification-code
189 Downloads
A simple way to authenticate a user using a verification code.
hrevert/ht-user-registration
4811 Downloads
A Zend Framework 2 module which extends the registration feature of ZfcUser with email address verification
exadium/emailverifiedmember
6 Downloads
This module provides a mechanism that requires users to verify their email address before they can log on to the CMS. This works with custom registration forms and the forum. Option for accounts to require manual moderation before they can log on.
cortex/auth
3499 Downloads
Cortex Auth is a frontend layer for the powerful authentication, authorization and verification package rinvex/laravel-auth on top of Laravel. It has all required controllers, views, routes, and other required assets to run a fully functional user management system with complete dashboard out of the box.
gammamatrix/playground-login-blade
396 Downloads
Playground: Provides an API and a Laravel Blade UI for authentication, authorization, credential updates and user verification.
naveed125/php-membership
17 Downloads
A simple secure user management library that supports things like signin, sign-out, sign-up, forgot-password and email-verification.
factpulse/sdk
63 Downloads
REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1, AFNOR PDP/PA, electronic signatures. ## π― Main Features ### π Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles** (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT), UBL 2.1 (OASIS) - **Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search) ### β Factur-X - Validation - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) ### βοΈ Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification ### π Flux 6 - Invoice Lifecycle (CDAR) - **CDAR Messages**: Acknowledgements, invoice statuses - **PPF Statuses**: REFUSED (210), PAID (212) ### π Flux 10 - E-Reporting - **Tax Declarations**: International B2B, B2C - **Flow Types**: 10.1 (B2B transactions), 10.2 (B2B payments), 10.3 (B2C transactions), 10.4 (B2C payments) ### π‘ AFNOR PDP/PA (XP Z12-013) - **Flow Service**: Submit and search flows to PDPs - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user ### ποΈ Chorus Pro - **Public Sector Invoicing**: Complete API for Chorus Pro ### β³ Async Tasks - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **Webhooks**: Automatic notifications when tasks complete ## π Authentication All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ``` ### How to obtain a JWT token? #### π Method 1: `/api/token/` API (Recommended) **URL:** `https://factpulse.fr/api/token/` This method is **recommended** for integration in your applications and CI/CD workflows. **Prerequisites:** Having set a password on your account **For users registered via email/password:** - You already have a password, use it directly **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API **Request example:** ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "[email protected]", "password": "your_password" }' ``` **Optional `client_uid` parameter:** To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`: ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "[email protected]", "password": "your_password", "client_uid": "550e8400-e29b-41d4-a716-446655440000" }' ``` The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client **Response:** ```json { "access": "eyJ0eXAiOiJKV1QiLCJhbGc...", // Access token (validity: 30 min) "refresh": "eyJ0eXAiOiJKV1QiLCJhbGc..." // Refresh token (validity: 7 days) } ``` **Advantages:** - β Full automation (CI/CD, scripts) - β Programmatic token management - β Refresh token support for automatic access renewal - β Easy integration in any language/tool #### π₯οΈ Method 2: Dashboard Generation (Alternative) **URL:** https://factpulse.fr/api/dashboard/ This method is suitable for quick tests or occasional use via the graphical interface. **How it works:** - Log in to the dashboard - Use the "Generate Test Token" or "Generate Production Token" buttons - Works for **all** users (OAuth and email/password), without requiring a password **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan **Advantages:** - β Quick for API testing - β No password required - β Simple visual interface **Disadvantages:** - β Requires manual action - β No refresh token - β Less suited for automation ### π Full Documentation For more information on authentication and API usage: https://factpulse.fr/documentation-api/
fen9li/laravel-user-activation
32 Downloads
Package for Laravel user account activation.
assada/laravel-user-verification
43 Downloads
User Email Verification For Laravel
rodshaffer/laravel-user-verification
16 Downloads
User Email Verification For Laravel 5.6.*