Hi everyone,
In version 8.1.3 we have an Eset in ITShop that grants group membership to different AD groups depending on the recipient's internal customer code. To avoid creating all groups objects in advance (they could be a long list), our script checks if the group exists and creates it before assigning the membership. If the product is assigned to one user then everything works fine. However if the product is requested for , let's say, two users at the same time , same customer code, and the group did not exist, the script runs for everyone of them and creates two identical groups in the table ADSGroup. They both have the same name, cn , attributes, even the ObjectGUID except the UID_ADSGroup. Each user if assigned to each group. The projection to AD works fine nonetheless, and in the target system we find only one group with two members (correct).
How could we avoid this? We have no way (as far as we know) of locking the record so the other simultanous process wont create a duplicate.Which would be your advice?
Thanks in advance,
Laura
Regards!
