Download the PHP package ems/permit without Composer
On this page you can find all versions of the php package ems/permit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package permit
Short Description Permission based authentication system
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package permit
Permit
Permission checking library and nice interfaces for access control.
Permit is a library to provide complete access control with permission-codes. Permission codes are just an array with some codes (strings) as keys and 1,0,-1 as values to allow, inherit and deny.
The main features and goals are:
- Have a nice top-level api to check permissions
- Always return a user, no matter if it is logged in or not (return a guest or system/cron user)
- Allow an secure and transparent "login-as-another-user" functionality
- Splits authentication and simple getUser()/setUser functionality
- Works with almost every other authentication system (Laravel, Sentry,...)
It works almost like Sentry, so why not Sentry instead of Permit?
- Sentry bybasses almost all auth functionalities of Laravel
- It sticks a lot of logic into the value objects (like user or group)
- Fat interfaces and therefore little chances to extend/modify it
- Never use a Facade which is named by a package ;-)
The Facade API (which is mostly used in views):
Internally the authentication interfaces are splitted into a container:
The next interface is a permission holder: (This could be a user or a group)
The extended version of ContainerInterface is the DualContainerInterface, which allows login as a different user.
