The PDP admin GUI was created because at the time there was no "Manage".
The PDP admin GUI is dated and needs rework in any case and costs effort to maintain a separate admin interface.
There's limited integration between PDP and the entities in Manage, so the admins have no overview of everything in one place.
Proposal:
PDP remains the (XACML) based policy engine that exposes an API to EB for decisions (so the actual Policy Decision Point)
PDP keeps its database which contains the running config of active states used in the critical path.
The Admin GUI (PAP) is integrated in Manage, so there's one interface to "manage" the platform re SP/IdPs and related configs. Manage maintains the 'truth' re policies in existence in a collection. A PUSH will also push updated rules to the PDP api for storage in the db as running config. Much like EB.
The Manage GUI will make use of the fact that Manage now knows about policies: configured policies are shown when you view an SP/RP, deleting or renaming an SP will not create orphaned rules, etc
Background:
Proposal: