Libraries tagged by user managements
neosrulez/frontendlogin
171 Downloads
A Neos CMS package that handles frontend login and user management.
mrpvision/gluu
564 Downloads
Package SCIM 2.0 User Management of the Gluu Server
meuhmeuhconcept/security-bundle
213 Downloads
Provides user management for Symfony3 Project.
mawuekom/laravel-usercare
63 Downloads
A Users Management Package that includes many features arround user
mapseven/neos-frontendusermanager
27 Downloads
Simple Frontend User Management with Registration and Login
laudis/usermanagement
1062 Downloads
Api for simple user management
lambda-platform/agent
79 Downloads
Lambda agent user management & authentication module
kumarrahul/rusermanagement
5 Downloads
This is a simple laravel package to implement user management
kkeiper1103/sentry-manager
30 Downloads
A Minimalistic, Laravel-Specific User Management Package. Provides User Registration, Login, and Update Views.
kategray/ldapuserbundle
1 Downloads
This bundle adds support for read and write user management in LDAP for FOSUserBundle.
jimblizz/extranet-bundle
6 Downloads
User management basics for corporate extranet development
igsem/api-core-bundle
37 Downloads
API Core for User management, login, security. Implements JWT and Guard Authenticator. User Crud, Company Crud a Simple CDN for file upload
flightsadmin/boilerplate
12 Downloads
CodeIgniter4 Boilerplate based on AdminLTE 3 with user management, roles, permissions, ...
encryptorcode/php-oauth-login
14 Downloads
An authentication framework which lets you to configure any type of authentication using OAuth (includes login with Google, Facebook, Github etc.) all with user management in your control.
eciboadaptech/finapi-webform
314 Downloads
The following pages give you some general information on how to use our APIs.The actual API services documentation then follows further below. You can use the menu to jump between API sections.This page has a built-in HTTP(S) client, so you can test the services directly from within this page, by filling in the request parameters and/or body in the respective services, and then hitting the TRY button. Note that you need to be authorized to make a successful API call. To authorize, refer to the 'Authorization' section of Access, or in case you already have a valid user token, just use the QUICK AUTH on the left.Please also remember that all user management functions should be looked up in Access.You should also check out the Web Form 2.0 Public Documentation as well as Access Public Documentation for more information. If you need any help with the API, contact [email protected] informationRequest IDsWith any API call, you can pass a request ID via a header with name "X-Request-Id". The request ID can be an arbitrary string with up to 255 characters. Passing a longer string will result in an error.If you don't pass a request ID for a call, finAPI will generate a random ID internally.The request ID is always returned back in the response of a service, as a header with name "X-Request-Id".We highly recommend to always pass a (preferably unique) request ID, and include it into your client application logs whenever you make a request or receive a response(especially in the case of an error response). finAPI is also logging request IDs on its end. Having a request ID can help the finAPI support team to work more efficiently and solve tickets faster.Type CoercionIn order to ease the integration for some languages, which do not natively support high precision number representations, Web Form 2.0 API supports relax type binding for the openAPI type number, which is used for money amount fields. If you use one of those languages, to avoid precision errors that can appear from float values, you can pass the amount as a string.FAQIs there a finAPI SDK?Currently we do not offer a native SDK, but there is the option to generate an SDKfor almost any target language via OpenAPI. Use the 'Download SDK' button on this page for SDK generation.Why do I need to keep authorizing when calling services on this page?This page is a "one-page-app". Reloading the page resets the OAuth authorization context. There is generally no need to reload the page, so just don't do it and your authorization will persist.