Skip to main content

XACML PEP configuration

Description

The PEP, Policy enforcement point,  is a component of policy-based management, where enforce the policies. It is the component that serves as the gatekeeper to access a digital resource. The PEP gives the PDP, Policy Decision Point, the job of deciding whether or not to authorize the user based on the description of the user's attributes.

Soffid allows you to configure differents policies enforcement points:

Screen

image-1627368437018.png

Custom attributes

Custom attributes for each PEP:

  • Enable XACML Policy Enforcement Point: select the Yes option to enable the PEP.
  • Policy Set Id: policy set identifier.
  • Policy Set Version: version of the policy set to enforce.
  • Trace requests: select the Yes option to enable the trace.

Policies enforcement points

Web Policy Enforcement Point

The policy will be enforced when the user open a new Soffid page.

 

Role centric Policy Enforcement Point

The policy will be enforced when the user login into Soffid. It will calculate the user authorizations as of the permissions that the user has assigned.

 

Dynamic role Policy Enforcement Point

The policy will be enforced when the user performs an action to evaluate if the user has or not authorization.

 You can use that PEP to split the permissions, for instance, a support group can update the permission of a specific group of user, and another support group can update the permissions of another group of users.

  • soffid object
  • method

External Policy Enforcement Point ( https://iam-sync-lab.soffidnetlab:1760//XACML/pep )

PEP of general purpose. Calling the web service, the clients can made validations.

 Attributes

token

method

resource

Password vault Policy Enforcement Point ( https://iam-sync-lab.soffidnetlab:1760//XACML/vault )

The policy will be enforced when the password vault is used.

 Operations

  • get
  • post

Attributes

token

accoi

Back to top