Here is some info I got from my colleague Tarun Tej, hopefully answers your questions. ?Jorge
There are two ways that a PyPDPServer (PEP) can receive a notification from PDP. 1) Through Websockets. We use websocket as internal mode of communication between PDP and PEP. (default) 2) It can also use UEB. callPDP method in turn makes a REST call to PDP component and returns back a response from PDP (XACML). The XACML response from PDP is converted back to Config /action or decision responses depending on the call made. The non-deprecated version of getDecision is getDecision(DecisionRequestParameters decisionRequestParameters). There are currently three calls that are supported by PEP (Policy XACML) 1) getConfig ? This is a configuration based policy. When made a request the response should give back a configuration if a permit. 2) getDecision ? This is a generic decision based policy. The response contains either a permit or deny. 3) sendEvent ? This is an action based decision policy. Where upon occurrence of few events (signatures) the POLICY can either perform an action or suggest an action to be taken by the PEP. Hope this answers all the questions here. Regards, Tarun Tej. From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Jingjing Zhang Sent: Tuesday, April 25, 2017 10:30 AM To: onap-discuss at lists.onap.org Subject: [onap-discuss] [Policy] PyPDPServer(PEP) get notification from XACML PDP I am wondering how does PyPDPServer(PEP) in XACML get notification from XACML PDP. PEP(PyPDPServer) queries XACML PDP using callPDP function in StdPolicyEngine.java. But how does PDP notify its decision to PEP? getDecision() in PolicyEngine.java is deprecated. sendEvent() function is not called by anyone. I didn't see how PEP get response from PDP. It's supposed to use either getDecision() or sendEvent(). But it looks like both are not called by anything else except tests. -- Regards! Zhang, Jingjing -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170426/64bf2104/attachment.html>
