12 lines
No EOL
870 B
Text
Executable file
12 lines
No EOL
870 B
Text
Executable file
== Policy Enforcers
|
|
|
|
PEP is a design pattern and as such you can implement it in different ways. {{book.project.name}} provides all the necessary means
|
|
to implement PEPs for different platforms, environments and using different programming languages. After all, {{book.project.name}} {{book.project.module}} is
|
|
fully RESTFUL-based, leveraging OAuth2 authorization capabilities to also support fine-grained authorization using a centralized authorization server.
|
|
|
|
image:../../images/pep-pattern-diagram.png[alt="PEP Overview"]
|
|
|
|
=== Download and Installation
|
|
|
|
The avaliable policy enforcers are distributed just like any other {{book.project.name}} Adapter. Please check this https://keycloak.gitbooks.io/securing-client-applications-guide/content/[documentation]
|
|
for more details about how to obtain and install these adapters accordingly with the platform you are using. |