We had an IDM 4.8.6 triggerless JDBC driver working in development.  After it was upgraded to 4.8.7, we found that it was throwing errors.  The Publisher Placement policy is based on the packaged policy and uses the Source Name token to derive a CN for the vault object:

<do-set-op-dest-dn>
    <arg-dn>
        <token-global-variable name="gcv.idv.person.ou"/>
        <token-text>\</token-text>
        <token-src-name/>
    </arg-dn>
</do-set-op-dest-dn>

The add event from the jdbc shim 4.2.2.0400 has a source dn like this: src-dn="PK_PARTY_NUMBER=12345678,table=DATAFEED_PERSONAL_DETAILS,schema=DBO"

The error message when the token-src-name is derived is:

Message:  Code(-9172) Error in PK_PARTY_NUMBER=12345678,table=DATAFEED_PERSONAL_DETAILS,schema=DBO : An invalid DN 'PK_PARTY_NUMBER=12345678,table=DATAFEED_PERSONAL_DETAILS,schema=DBO' is specified: DN does not conform to the format required by the current context.

We can also replicate this error in Designer Policy Simulator (4.8.7 and 4.9), and it seems to trigger for any values where there are more than one comma separated element.  I can see this working correctly on 4.8.6 versions, so think this should work in 4.8.7.  Obviously, we could change the policy to use an operational attribute, but this might be impacting many driver, so think it worth asking.

Has this been seen elsewhere?  Is it replicable issue?