@jose.cruz

Thank you for reaching out to us.

You can call the AuthorizationAgent::getPeToSubServiceList() method to look up within the Refinitiv Real-Time Data Access Control System, the PE to subservice authorization values that were assigned to the referred to service.

Then, you can call the the AuthorizationAgent::getUserSubServiceList() method to look up within the Refinitiv Real-Time Data Access Control System, the subservice authorization values, known as AIS list, that were assigned to the referred to user based on the supplied handle.

Next, you can develop an application logic to perform CBE permissions checks based on those information.

However, OpenDACS API also generates the DACS usage files used by DACS to generate DACS reports for auditing. Therefore, if you don't use OpenDACS API to check permissions, DACS will not generate the reports for auditing. You may need to contact your DACS administrator or LSEG account team to verify this kind of usage.

Thank you for your answer.

I'm not using the getPeToSubServiceList nor getUserSubServiceList, my CBE permissions check is being based on the tutorial provided: I create the lock and use CheckSubscription.
But what I was going to do is after I check the permissions, I would cache the result so the application doesn't need to check it everytime I refresh the live data.
Is this a valid solution? And does it give me any advantage, since I've read that OpenDacs does it's own caching?

When you say auditing process, You mean the DACS auditing the user log in?
Because the user would remain logged in I believe, does DACS audits the permission checks as well? Is that what I need to find out?
Regarding the OpenDACS caching, do you know if it has internal caching already?