Bug Report
An accessPolicy requiring non-default VC scope always fails because EDC will request only the default VC scopes for Catalog requests.
Expected Behavior
The VCs scopes include all needed scopes to verify the accessPolicy for all offers during a Catalog request.
Observed Behavior
Only "generic" VC scopes (ones that are in the default DCP scope) are requested.
Context Information
Detailed Description
I don't know how to fix it, but I traced down the problematic code path:
The getCatalog method calls protocolTokenValidator.verify() with a blank RequestCatalogPolicyContext here. This results in an incorrect verificationContext built here, hence incorrect VCs requested.
Later during datasetResolution here, the policy is being evaluated but the credentials fetched will be insufficient and policy validation will fail.
Bug Report
An
accessPolicyrequiring non-default VC scope always fails because EDC will request only the default VC scopes for Catalog requests.Expected Behavior
The VCs scopes include all needed scopes to verify the accessPolicy for all offers during a Catalog request.
Observed Behavior
Only "generic" VC scopes (ones that are in the default DCP scope) are requested.
Context Information
Detailed Description
I don't know how to fix it, but I traced down the problematic code path:
The
getCatalogmethod callsprotocolTokenValidator.verify()with a blankRequestCatalogPolicyContexthere. This results in an incorrect verificationContext built here, hence incorrect VCs requested.Later during datasetResolution here, the policy is being evaluated but the credentials fetched will be insufficient and policy validation will fail.