Skip to content
This repository has been archived by the owner on Dec 7, 2020. It is now read-only.

Commit

Permalink
- updating the README to reflect the changes
Browse files Browse the repository at this point in the history
  • Loading branch information
gambol99 committed Jul 3, 2018
1 parent 92bdbd0 commit aa7c721
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
#### **2.2.3 (Unreleased)**

FEATURES:
* Added the ability to use a "any" operation on the roles rather then just "and" with the inclusion of a `require-any-role` [#PR387](https://github.com/gambol99/keycloak-proxy/pull/387)
* Added the ability to use a "any" operation on the roles rather then just "and" with the inclusion of a `require-any-role` [#PR389](https://github.com/gambol99/keycloak-proxy/pull/389)

#### **2.2.2**

Expand Down
5 changes: 4 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -217,6 +217,7 @@ resources:
roles:
- client:test1
- client:test2
require-any-role: true
groups:
- admins
- users
Expand Down Expand Up @@ -253,7 +254,9 @@ bin/keycloak-proxy \
--resources="uri=/public/*|white-listed=true"
```
Note from release 2.2.0 the `--enable-default-deny` is true by default and should explicityly allow what you want through.
Note from release 2.2.0 the `--enable-default-deny` is true by default and should explicitly allow what you want through.
By default the roles defined on a resource perform a logical `AND` so all roles specified must be present in the claims, this behavior can be altered by the `require-any-role` option however so as long as one role is present the permission is granted.
#### **HTTP Routing**
Expand Down

0 comments on commit aa7c721

Please sign in to comment.