PROD_PERM and PEList

philippe.mesmeur · 2024-12-04T15:43:31+00:00

There was an error rendering this rich post.

Hello,

I use the Java/RefinitivSDK 3.7.0.0 in order to receive RealTime data from TREP.

Once a RealTIme data is subscribed, the API notifies me through my implementation of the interface method OmmConsumerClient.onRefreshMsg(RefreshMsg refreshMsg, OmmConsumerEvent event)

The RefreshMsg argument provides:

the permission of the RealTime data (cf method ByteBuffer RefreshMsg.permissionData())
and also a PROD_PERM, that is an integer obtainable by getting the value of the field "PROD_PERM" (fields are obtained by calling refreshMsg.payload().fieldList())

For example, when subscribing to CZK2MD=, I get

permissionData: { 0x03, 0x01, 0x01, 0x28, 0x70, 0xC0 }
PROD_PERM: 2870

Today, I use the permissionData in order to "know" whether a user is allowed to use the RealTime data. Do do so, I use Java/RFA 8.2.1.L3 with something like:

    ByteBuffer dacsPermission;
    byte[] arr = new byte[dacsPermission.remaining()];
    dacsPermission.get(arr);
    AuthorizationLock authorizationLock = new AuthorizationLock(arr);

    ... 
    
    byte[] dacsLock = authorizationLock.getAuthorizationLock().clone();

    ...
    
    AuthorizationCheckResult authCheckResult =
            agent.checkSubscription(handle,
                    AuthorizationUsageType.DONT_PERFORM_USAGE_LOGGING,
                    AuthorizationRequestType.NORMAL_REQUEST_LOGGING,
                    new AuthorizationCheckStatus(),
                    "IDN_SELECTFEED",
                    "",
                    dacsLock);

    boolean isAuthorized = (authCheckResult == AuthorizationCheckResult.ACCESS_ALLOWED);

I would like to know if it is possible get the same information using the PROD_PERM instead of the permissionData.

Thank you to also explain the difference and/or the relationship between PROD_PERM and permissionData

Regards

Philippe

Find more posts tagged with

java

DACS

permissioning

ema-api

pe-code

refinitiv-realtime-sdk

#technology

Accepted answers

Gurpreet

prod perm contains the PE code, which can be used to generate the dacs lock

AuthorizationLock authLock = new AuthorizationLock( serviceID, AuthorizationLock.OR, vPEList );
byte[] dacsLock = authLock.getAuthorizationLock();

Why won't you want to use the permission data?

Jirapongse

A DACS Lock contains both a service ID and PEs. Therefore, to access the data, users must have permission for both a service and content.

Yes, you can use the getServiceAttributes to get service IDs. For example:

11:06:55	AuthorizationAgent::getServiceAttrbutes() return successfulLookup

11:06:55	Service Attributes Result:

		ID 		 Name 	 QOS 	 Type 	 Vendor

=================================================================

		257 		 ATS1_7 	 R:0 	 SC 	 IDN

		8093 		 ELEKTRON_RDF 	 R:0 	 SC 	 IDN

		8590 		 ELEKTRON_DD 	 R:0 	 SC 	 IDN

All comments

Gurpreet

Hello Philippe,

The field PROD_PERM contains the PE code for the item and can also be used for entitlement checks, although the permission data is a better option. This question and this one has more information about it.

philippe.mesmeur

*-Hello,

First of all, thank you for this quick answer

I am currently investigating the links you provided me.

As I understand in your answer and also in PROD_PERM and DACS lock, it is possible to use whether permData or PROD_PERM, but it is better to use permData

However, I do not really understand the answer to the question:

Q: Any specific reason it is preferred to use permission data from refresh over PROD_PERM?
A: With PROD_PERM, the client needs to use OpenDACS API to create a DACS lock from the PE. Then use the created DACS lock to perform CBE checks.

Indeed, I think that for me, it would be really better to use PROD_PERM instead of permission data. (In the example I gave yesterday, I think it would be better for me to use PROD_PERM: 2870 instead of permissionData: { 0x03, 0x01, 0x01, 0x28, 0x70, 0xC0 }). Do think it could be a problem?

Currently, the only thing I do with the permissionData is to create an AuthorizationLock. I would need to do the same from a PROD_PERM

I tried to find how to do it but I didn't: can you explain me how to create an AuthorizationLock from a PROD_PERM

Thank you

Gurpreet

prod perm contains the PE code, which can be used to generate the dacs lock

AuthorizationLock authLock = new AuthorizationLock( serviceID, AuthorizationLock.OR, vPEList );
byte[] dacsLock = authLock.getAuthorizationLock();

Why won't you want to use the permission data?

Jirapongse

A DACS Lock contains both a service ID and PEs. Therefore, to access the data, users must have permission for both a service and content.

Yes, you can use the getServiceAttributes to get service IDs. For example:

11:06:55	AuthorizationAgent::getServiceAttrbutes() return successfulLookup

11:06:55	Service Attributes Result:

		ID 		 Name 	 QOS 	 Type 	 Vendor

=================================================================

		257 		 ATS1_7 	 R:0 	 SC 	 IDN

		8093 		 ELEKTRON_RDF 	 R:0 	 SC 	 IDN

		8590 		 ELEKTRON_DD 	 R:0 	 SC 	 IDN

philippe.mesmeur

Every thing is perfectly clear now

If I have additional questions I'll come back to you

Thank you

Philippe

EXPLORE OUR SITES