Not a bug
Outgoing pre-provisioning task is called for some joined users
Adrian Corston 1 year ago in UNIFYBroker/Plus • updated by Beau Harrison (Senior Product Software Engineer) 1 year ago • 4
In my customer's TEST environment they are seeing AD sAMAccountName being updated for existing users where the join criteria are met. The only place where the sAMAccountName is set is in the outgoing pre-provisioning task, which should not be called for existing joined entities.
I have also seen a second confirmation that the task is being called for pre-existing users: the "AD Account Creation" notifications being repeatedly sent for a large number of entities every time a Baseline Sync is performed. The only place where that notification is sent is in that same outgoing pre-provisioning task.
Customer support service by UserEcho
Affected customer environment is Metlifecare TEST.
Example join is f4cc6eb9-b958-4d4c-aace-15dff3ded3ef (locker) / b1f0f716-2267-41c2-bb44-32d352445a32 (adapter)
Please put this ticket on hold for a bit. Subsequent investigation has identified that the original AD account may not have been loaded correctly, so the provisioning may have been legitimate.
Please cancel this ticket.