message: Remove permissions from 1.0.0
diff: @@ -41,74 +41,6 @@ If you want to only turn on logs for a specific hook, middleware or service you
  `DEBUG=feathers-authentication:hooks:authenticate npm start`
  ```
  -
  -## Better Permissions Control
  -
  -We have introduced 3 new hooks and 2 new middleware as part of [feathers-permissions](https://github.com/feathersjs.com) that give you much more flexibility and control over access permissions than was previously possible. Permissions are stored in the database on the entity record that needs to have access permissions checked (typically a user). They look like this:
  -
  -```js
  -[
  - '*', // all services, all methods, all docs
  - 'users:*', // all methods on users service
  - 'users:remove:*', // can remove any user
  - '*:remove', // can remove on any service
  - 'users:remove:1234', // can only remove user with id 1234
  - 'users:*:1234' // can call any service method for user with id 1234
  -]
  -```
  -
  -you use your hooks like this:
  -
  -```js
  -const permissions = require('feathers-permissions');
  -userService.hooks({
  - before: {
  - all: [
  - permissions.hooks.checkPermissions({service: 'users', on: 'user', field: 'permissions'}),
  - permissions.hooks.isPermitted()
  - ]
  - }
  -});
  -userService.hooks({
  - after: {
  - create: [
  - permissions.hooks.setPermissions({permissions: ['users:*:[id]'], field: 'permissions'})
  - ]
  - }
  -});
  -```
  -
  -and the middleware like this:
  -
  -```js
  -const permissions = require('feathers-permissions');
  -const requiredPermissions = ['users:*', 'admin']; // whatever permissions you want
  -app.get(
  - '/protected',
  - permissions.express.checkPermissions({
  - on: 'user',
  - field: 'permissions',
  - permissions: requiredPermissions
  - }),
  - permissions.express.isPermitted,
  - (req, res, next) => {
  - // Do your thing
  - }
  -);
  -```
  -
  -By default this new hook and new middleware assume you are storing your permissions on a `permissions` field either as an array of strings or a string with comma separated permissions. As always, you can customize the field you are storing your permissions under so you can still use the old role based system by doing this:
  -
  -```js
  -const auth = require('feathers-authentication').hooks;
  -userService.before({
  - all: [
  - auth.isAuthenticated(),
  - auth.checkPermissions({roles: ['admin'], on: 'user', field: 'role'})
  - ]
  -});
  -```
  -
  ## More Flexible Tokens
  Previously JWT's were only used as an access token and could only be created as part of the authentication flow. This is still the default, however it's now possible to create JWTs with different options for all sorts of things like password reset, email verification, magic links, etc.
  