Download the PHP package dotkernel/dot-authorization without Composer
On this page you can find all versions of the php package dotkernel/dot-authorization. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dotkernel/dot-authorization
More information about dotkernel/dot-authorization
Files in dotkernel/dot-authorization
Package dot-authorization
Short Description DotKernel authorization service abstractions
License MIT
Homepage https://github.com/dotkernel/dot-authorization
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 dot-authorization
dot-authorization
Authorization base package defining interfaces for authorization services to be used with DotKernel applications.
Installation
Run the following command in you project directory
Please note that usually this pacakge will be installed as a dependency to a concrete implementation, so you won't need to add this to your project manually.
AuthorizationInterface
Defines the interface that should be implemented by any authorization service, in order to work with DotKernel applications. This is a result of the fact that, by default, any DotKernel package which has to do with authorization is assuming that a service is registered in the service container using as service name this interface's FQN
Methods
- this is the only method that deals with authorization. Given a permission and a list of roles, should return a boolean value of true if at least one role has access to the requested permission. As you can see, we expect that the authorization service to be implemented as an RBAC.
RoleInterface
Defines the interface that Role objects must implement. A role object should be able to retrieve its name, so this interface has only one method defined
IdentityInterface
Interface that needs to be implemented by entities that support roles. They should be able to retrieve their roles by defining a getRoles() method.
The roles should be an array of role names or role objects
This package is suitable for RBAC style authorization. Roles can be flat or hierarchical and they are assigned permissions. A role is granted if it has the required permission.
ForbiddenException
Exception to be thrown when accessing content without having the required permissions. This can be used withing an application to trigger a forbidden error and do a custom action(like displaying a forbidden page or redirecting). This package does not define how you should handle such situations. There is a concrete authorization implementation in dot-rbac and a forbidden exception handler in dot-rbac-guard as DotKernel default packages for authorization.
