-
Notifications
You must be signed in to change notification settings - Fork 2
Home
▶️ Getting Started (this page)- ⏬ Deploy and Configure the PEP
- ⏬ Chart Configuration
- ⏬ Platform Resource Management
- ⏬ Integration Guide
- ⏬ Access Enforcement
- ⏬ Swagger API
The PEP Service is packaged and delivered as a Docker container.
You can either
👷♀️ Build and deploy your own PEP Service
or
🚢 Use the latest release version available on Docker Hub as eoepca/um-pep-engine:latest
In this guide, we assume using a locally packaged Policy Enforcement Point (PEP) so we will refer to um-pep-engine:latest as the docker image. Please substitute with your image tag.
The PEP can serve as a self-standing capabilities catalogue but, in order to intercept and enforce policy-based access control based on UMA the following endpoints need to be configured:
- OIDC and UMA Endpoints (exposed by a Login Service), enabling ticket generation and Policy Enforcement
If you do not have these endpoints available, please follow the Login Service wiki to setup a dedicated instance.
The PEP service is a component that runs ad-hoc to each Platform Resource Server and enforces policy-based access control, allowing Resource Owners, and Resource Servers to register and manage their Platform resources (endpoints, operations, offerings...).
⏭️ Next step: Deploy and Configure the PEP