Download the PHP package wassa/apikey-authenticator-bundle without Composer
On this page you can find all versions of the php package wassa/apikey-authenticator-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download wassa/apikey-authenticator-bundle
More information about wassa/apikey-authenticator-bundle
Files in wassa/apikey-authenticator-bundle
Package apikey-authenticator-bundle
Short Description Wassa ApiKeyAuthenticatorBundle
License MIT
Homepage http://wassa.io
Informations about the package apikey-authenticator-bundle
Wassa API Key Authenticor Bundle
The Symfony website has a great tutorial on how to create an API token authentication system. It's crystal clear and very easy to reproduce. From our point of view though, it has 2 main issues:
1) If you have a lot of projects (which is our case at Wassa), it can be quite time consuming to reproduce it for every single project 2) The tutorial is more targeted toward what we call "multi-users" environment, in which a single API is linked to a single user.
This bundle aims to address these 2 issues.
Requirements
- Symfony 2.8
Installation
First run:
Then update AppKernel.php
:
The API key must be stored in var/private/api.key
. You can create the file yourself or use the built-in command to create a key:
If you don't provide an API key, the command will use the default generator (see "Creating your own generator") to create a random key.
The default size for the random key is 32 chars but can be configured (see "Configuration") or manually set it with the -s
switch.
Remember to set correct permissions on the key file so that it is readable only by the webserver.
Configuration
The bundle works without any special configuration. Add and edit the following block to config.yml
if necessary:
The name
parameter specify the name of the "field" in the request containing the API key.
The location
parameter specifies which "field" to look for the API key in the request:
headers
: look for an HTTP headerquery
: look for a query parameterbody
: look for a POST data parameterall
: look for all above and returns the first found (in order above)
location
can be a combination of different values, for example 'headers&query'
to look in headers and query but not in the body.
Then edit security.yml
:
Be sure that access_control
is configured with the same role as in config.yml
.
Creating your own API key generator
If you need your API key to be a bit more complex than a series of X chars, you can create your own generator.
In order to do that, just create a service that implements ApiKeyGeneratorInterface
and write your own logic in the generate()
method.
Then configure the bundle in config.yml
:
Composer post-install script
You can automate the creation of the API key by including the built-in post-install script in your composer.json
:
apikey-size
is optional, if you don't specify it, the key will be created with the configured key size.
Also, if an API key already exists, it will not be overriden.
Managing multiple API keys
For now our bundle handles only one API key, that's what it was made for in the first place so it's OK. If you want to handle multiple keys, then you can just follow these easy steps:
- Create your own User class that implements our
ApiKeyUserInterface
and provide an implementation forgetApiKey()
- Create your own UserProvider class or use one that suits you (like FOSUserBundle).
This part of the tutorial can help you to do that.
All versions of apikey-authenticator-bundle with dependencies
symfony/framework-bundle Version ~2.8|~3.0|~4.0
symfony/security Version ~4.0