Problem with local BPS groups (Synchronisation?)

0

Hi Ernst,

I can't help you with it, but I can say that you are not alone.

We have a few environments where we have a large delay when the user membership is updated. The only thing common in these environments is, that there are multiple content databases. When we are updating the group membership we use the Designer Studio and open the content database where the group is used. This way the changes are directly available in the database and the rest of the databases will be updated some time later.

Best regards,
Daniel

Thanks Daniel!
Some of these groups are created 2 or more weeks ago. Since the application (where these groups are used) was not deployed into production, I didn't notice this problem.

We have a simple on prem installation with one content database.

Maybe someone from WEBCON could provide some infos, what (logs, etc.) should be checked.
Interessing: in the studio, these local groups are marked as sync'd (with a current time stamp). In the web-admin they are shown with the hour-glass icon.

After some digging I found one entry in table [UserSynchronisationQueueItems] with an USQ status 100. But this entry is from 2024-10-17 ... not sure if this could block a complete synchronisation.

I also checked [BpsUsersGroupRelations]:
prod and dev-stage: emtpy in content-db, correct values in config-db

When it comes to synchronizing multiple content databases, I use user updates via the REST API to synchronize groups. This makes it work much faster for us, and there is no need to update anything in DS.

Try adding/removing users using the REST API
/api/data/v6.0/admin/group/members/add
/api/data/v6.0/admin/group/members/remove

Hi Krystian,

a word of caution regarding the api calls. It’s possible to add the same user multiple times to the same group. There’s no check.

At least it was in 2023 and the feedback was that this behavior would not be changed. In the background a sync task is triggered automatically. I added a check whether this task had been completed before I allowed the users to do any further updates.


Best regards,
Daniel

It seems there is a bigger problem with group/user sync in our production environment (we have a ticket @Webcon open - via our service provider).

I get correct members using GROUP MEMBERS (group), but CURRENT USER IS ONE OF does always return false. Even the privileges are not working with groups. I Had to add users directly to the instances.

Currently I have 2 apps ready, but cannot deploy them into production.

I hope WEBCON is reacting to our ticket soon.

Ernst

Hi Daniel,
I haven't encountered the problem you described, because every time we add a REST action to groups, we always apply the rule of checking who is in the group, and if a person is already there, we don't add them again – this is a security measure and prevents what you described – adding one person multiple times to the same group.

Best regards,
Krystian

Can someone at WEBCON please check our Ticket (openend via our provider DCCS).. its open since 3-4 weeks now..

Currently we are not able to deploy new applications, because the groups (ad and bps groups) are not evaluated.

According to the sync-debug log, the sync-process runs through without any errors. However the bps groups have the sand-clock icon in the web-admin view.

I guess the error entry in the table UserSynchronisationQueueItems is preventing the sync process to finish correctly.

Thanks

P.S.
Off course I could provide a remote-session to look into the details