keycloak-scim/authorization_services/topics/enforcer/overview.adoc

[[_enforcer_overview]]
== Policy Enforcers

Policy Enforcement Point (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 programming languages. {{book.project.name}} {{book.project.module}} presents a RESTful API,
and leverages OAuth2 authorization capabilities for fine-grained authorization using a centralized authorization server.

image:../../images/pep-pattern-diagram.png[alt="PEP Overview"]
[RHSSO-599] - Replacing link with fake 2016-11-29 15:30:53 +00:00			`[[_enforcer_overview]]`
Servlet security quickstart 2016-06-03 23:49:26 +00:00			`== Policy Enforcers`

[KEYCLOAK-3546] - A lot of fixes and improvements to docs from srehorn. 2016-09-09 03:53:39 +00:00			`Policy Enforcement Point (PEP) is a design pattern and as such you can implement it in different ways. {{book.project.name}} provides all the necessary means`
General cleanup and edits of the documentation 2016-11-15 21:34:20 +00:00			`to implement PEPs for different platforms, environments, and programming languages. {{book.project.name}} {{book.project.module}} presents a RESTful API,`
[KEYCLOAK-3546] - A lot of fixes and improvements to docs from srehorn. 2016-09-09 03:53:39 +00:00			`and leverages OAuth2 authorization capabilities for fine-grained authorization using a centralized authorization server.`
Servlet security quickstart 2016-06-03 23:49:26 +00:00
More screenshots. Reviewing getting started tutorials. 2016-06-14 23:50:50 +00:00			`image:../../images/pep-pattern-diagram.png[alt="PEP Overview"]`