davidgelhar commented 4 days ago
If you configure a Duo provisioner to sync the 'realname' Duo attribute, for example:

provisioner.duo_user.targetEntityAttribute.3.name = name

provisioner.duo_user.targetEntityAttribute.3.translateExpressionType = grouperProvisioningEntityField

provisioner.duo_user.targetEntityAttribute.3.translateFromGrouperProvisioningEntityField = name 

the provisioner will detect when the attribute is out of sync and attempt to update it, but the change will not be included the the HTTP post. This appears to be the same problem reported in slack by David Jardim https://internet2.slack.com/archives/C7V0UQDJ4/p1710523466936369

Problem is that updateDuoUser is looking at fieldsToUpdate to decide what fields to include in the update, and it needs to look for name instead of realname