Unable to see newly created contact Definition under catalog browser of consumer connector

[Akshay-a-j]

Hello,
"I've created a new policy definition by integrating a freshly created policy type, implementing all required modifications in both the frontend and backend. Additionally, I've associated an asset with it. Despite these efforts, the new policy definition isn't visible in the consumer connector's catalog browser. Upon reviewing the logs for edc-extensions-edc-1 and edc-extensions-edc2-1, I didn't encounter any errors. Could you guide me on which logs should be examined and the process to confirm the proper functioning of my new policy type within this edc-extensions configuration?"

[tmberthold]

Hi, could you give us some more information about what kind of policy you developed?
If the policy does not allow the consumer to view the offer, the consumer will not display it in the catalog. Maybe the consumer fails the validation of the self-created policy.

[Akshay-a-j]

"It resembles the 'Connector-Restricted-Usage' setup. I have focused on the frontend (edc-ui), which is working fine. To ensure smooth operation on the backend, I have created the following files."
ParticipantIdPolicyExtension.java

package de.sovity.edc.extension.policy;

import org.eclipse.edc.policy.engine.spi.PolicyEngine;
import org.eclipse.edc.policy.engine.spi.RuleBindingRegistry;
import org.eclipse.edc.policy.model.Permission;
import org.eclipse.edc.runtime.metamodel.annotation.Inject;
import org.eclipse.edc.spi.system.ServiceExtension;
import org.eclipse.edc.spi.system.ServiceExtensionContext;

import static org.eclipse.edc.policy.engine.spi.PolicyEngine.ALL_SCOPES;

public class ParticipantIdPolicyExtension implements ServiceExtension {

    private static final String KEY_PARTICIPANT_ID_RESTRICTED = "PARTICIPANT_ID_RESTRICTED";
    private static final String EXTENSION_NAME = "Policy Function: PARTICIPANT_ID_RESTRICTED";

    @Inject
    private RuleBindingRegistry ruleBindingRegistry;

    @Inject
    private PolicyEngine policyEngine;

    @Override
    public String name() {
        return EXTENSION_NAME;
    }

    @Override
    public void initialize(ServiceExtensionContext context) {
        var monitor = context.getMonitor();

        ruleBindingRegistry.bind("USE", ALL_SCOPES);
        ruleBindingRegistry.bind(KEY_PARTICIPANT_ID_RESTRICTED, ALL_SCOPES);

        policyEngine.registerFunction(
                ALL_SCOPES,
                Permission.class,
                KEY_PARTICIPANT_ID_RESTRICTED,
                new ParticipantIdPolicyEvaluator(monitor));
    }
}

and
ParticipantIdPolicyEvaluator.java

package de.sovity.edc.extension.policy;

import org.eclipse.edc.policy.engine.spi.AtomicConstraintFunction;
import org.eclipse.edc.policy.engine.spi.PolicyContext;
import org.eclipse.edc.policy.model.Operator;
import org.eclipse.edc.policy.model.Permission;
import org.eclipse.edc.spi.monitor.Monitor;

public class ParticipantIdPolicyEvaluator implements AtomicConstraintFunction<Permission> {
    private final Monitor monitor;

    public ParticipantIdPolicyEvaluator(Monitor monitor) {
        this.monitor = monitor;
    }

    @Override
    public boolean evaluate(Operator operator, Object rightValue, Permission rule, PolicyContext context) {
        // Hardcoded participant ID for testing
        String hardcodedParticipantId = "my-edc2";
    
        if (rightValue instanceof String) {
            return hardcodedParticipantId.equals(rightValue);
        } else if (rightValue instanceof String[]) {
            String[] restrictedIds = (String[]) rightValue;
            return Arrays.asList(restrictedIds).contains(hardcodedParticipantId);
        } else {
            monitor.severe("Invalid type for rightValue, expected a String or String[] representing participant ID(s).");
            return false;
        }
    }
}
```

And I registered the same under "META-INF/services". 

[tmberthold]

Did you take a look at the value of the rightValue, maybe it's just not equal to hardcodedParticipantId or hardcodedParticipantId is not in restrictedIds? Have you tried some debugging around that?

Also be aware, that the referenced policy itself is currently not working: #727

[Akshay-a-j]

Okay! I'll verify if the values match.
Thank you