Add user to bps group action: Times out in synchronous mode

0

I overlooked something.
The action triggers the synchronization of the group and afterwards the synchronization of the added user. This started a download from Azure AD which causes the delay.
- (7/2/2024 2:33:46 PM) Step started: Download selected objects from Azure AD if required
- (7/2/2024 2:35:44 PM) Step completed: Download selected objects from Azure AD if required (duration: 118687 ms)

What's interesting is that changing the group members via the Portal creates only one synchronization job /entry.

Improving the download from Azure AD is probably not possible, so we will have to cope with this.

Hi,

Why it takes so long I don't know, but for this reason I use the api method to add a user to a group.

/api/data/v5.0/admin/group/members/add

It works fast and performs synchro of all DB_Content databases

Regards.

Hi Karol,

I have thought about it and also making the action asynchronous. It should work in theory but I'm having second thoughts about it because of a theoretical problem.
If the synchronization doesn't finish before the workflow instance is updated again, the user may get added twice to the BPS group.

It's probably not a real issue and I may decide to change the current configuration.

Best regards,
Daniel

Hi,
It seems to me that synchronization occurs automatically for all databases using this method (I'll check it in my free time).
I check the user directly in the database config dbo.BpsUsersGroupRelations, then I am sure if he is or not in the group.

Regards.