We have a vault, that has users with two CN values. a text based name
like geoffc, and an employee ID based name, like e123456.

Since they were all created with the text based name (geoffc), they have
that as the naming attribute.

But we want to login via Client 32 by the employee ID going forward, and
that has been very inconsistent... So the postulated resolution is get
rid of the text based name, (or store it elsewhere), and just use the
employee ID value instead as the CN value.

But this is a change to the naming attribute, isn't it?

Would a simple modify of the CN attribute do the trick, or since the
attr is current @naming="true", are we required to do a rename event?

Thousands of renames is potentailly painful, whereas thousands of
attribute changes is pedestrian, and an every day event...