2016-11-29 15:30:53 +00:00
|
|
|
[[_enforcer_overview]]
|
2017-10-09 06:38:46 +00:00
|
|
|
= Policy Enforcers
|
2016-06-03 23:49:26 +00:00
|
|
|
|
2017-08-28 12:50:14 +00:00
|
|
|
Policy Enforcement Point (PEP) is a design pattern and as such you can implement it in different ways. {project_name} provides all the necessary means
|
|
|
|
|
to implement PEPs for different platforms, environments, and programming languages. {project_name} Authorization Services presents a RESTful API,
|
2016-09-09 03:53:39 +00:00
|
|
|
and leverages OAuth2 authorization capabilities for fine-grained authorization using a centralized authorization server.
|
2016-06-03 23:49:26 +00:00
|
|
|
|
2017-10-09 06:38:46 +00:00
|
|
|
image:images/pep-pattern-diagram.png[alt="PEP Overview"]
|
