The error seems to say it wants a GCV.  The example you show, based on where you say it resides, suggests it is in as a Driver Configuration value.  (By the way, the parent, Sub, and Pub sections are read different in the Java shim, so location in there can matter as well) .

You can copy the values to the GCV with little to no effect.

Hello Geoffrey,

Looks like adding the missing variables in the GCV fixed the issue, the driver starts now:

Here is the lines I've added in the GCV:

<?xml version="1.0" encoding="UTF-8"?><configuration-values>
<definitions>
<definition display-name="drv.team.user.owner" name="drv.team.user.owner" type="string">
<description/>
<value></value>
</definition>
<definition display-name="drv.channel.user.owner" name="drv.channel.user.owner" type="string">
<description/>
<value></value>
</definition>
<definition display-name="drv.entitlement.channel.name" name="drv.entitlement.channel.name" type="string">
<description/>
<value></value>
</definition>
</definitions>
</configuration-values>

Thanks

Sylvain

You might have been bitten by a package bug or a designer glitch. Suspect this is just a missing linkage. Or changes applied to wrong IDM server (GCVs and driver params are server specific).

These settings are set in a GCV object, which needs to be linked into the driver, and that linkage needs to be deployed.

IIRC these options were added a few patch revisions ago. They are relatively fresh.

As Geoffrey mentioned these gcv-ref entries mean that the driver params are looking for entries in a corresponding GCV object.

You shouldn't need to add these entries to the built.in GCV object like you have, that will allow the driver to start, but you will run into similar issues with the next upgrade. The real solution is to ensure that packaged GCV object is present, linked to the driver and deployed. Then you can remove your emergency solution as described above.

The package GCV seems to be installed, don't know why the settings did not apply properly.

You are missing an Entitlements package. Install the relevant one for your scenario and these problems should go away.

This is a bit of a poor design decision to reference GCVs from another package (which looks to be optional, but probably isn't) in the driver base configuration.