today I found another bug in the current Designer 4.6.1 (LDAP). According to the IDM 4.6.1 release notes only the LDAP version of Designer should be used - so I am just following this "recomandation"

The bug is coming up when configuring a new map-token in argument builder. After browsing the map object I can see, that the browse function is returning a LADP DN, but this can not be stored in the DN parameter of the map-token.

For one or the other reason filling in the dn in the slash format seams to work neither.

The only work-around I found so far is to copy/paste the configured token from an existing policy - or hacking in the xml code manually!

Does anybody else saw this issue or even better found a solution to use the UI, again?

Kind regards,