0
Fixed

Google Groups - Clearing External Membership

Boyd Bostock 4 years ago in UNIFYBroker/Google Apps updated by anonymous 4 years ago 6

Clearing all External Members from Google Groups is not working, there is no error reported during the export however membership remain unchanged.

Affected Versions:
Fixed by Version:

Answer

Answer

Hi Boyd

I've found that this issue was being caused by a defect which has already been fixed and is included in Identity Broker v5.0.5 RC1. Are you able to upgrade to this version?

I have managed to make the example group the only MIM Export and started a new log file (below).


20170111,00:19:46,UNIFY Identity Broker,LDAP Engine,Information,A client has connected to the LDAP endpoint from address: 127.0.0.1:56935.,Normal
20170111,00:19:46,UNIFY Identity Broker,Connector,Information,"Request to add entity to connector.
Request to add entities [Count:1] to connector Google Groups (Staff) Connector.",Normal
20170111,00:19:46,UNIFY Identity Broker,Connector,Information,"Add entities to connector completed.
Add entities [Count:1] to connector Google Groups (Staff) Connector reported 1 entities saved. Duration: 00:00:00.0468038",Normal
20170111,00:19:47,UNIFY Identity Broker,Change detection engine,Information,"Change detection engine unscheduled started.
Change detection engine unscheduled for connector Google Groups (Staff) Connector started.",Normal
20170111,00:19:47,UNIFY Identity Broker,Change detection engine,Information,"Change detection engine unscheduled completed.
Change detection engine unscheduled for connector Google Groups (Staff) Connector completed. Duration: 00:00:00.0780032",Normal

Hi Beau

I have captured traffic using RawCap , it is 24MB where should I put it?

I am not very familiar with analysing pack traces, however I cannot see any internet traffic, given the speed at which the exports occur it may be possible that the web service call to Google is not actually made.

Boyd


Under review

You can drag in into a reply here and it will upload.

I also suspect that the service call isn't being made as I was able to successfully perform the operation using the connector test harness. Doing so even with no change took several seconds to complete so the instant completion seen in your logs would indicate the issue is further back. The LDAP traffic between MIM and IdB is what I need from the trace to see if the change data is correctly getting to IdB.

Answer

Hi Boyd

I've found that this issue was being caused by a defect which has already been fixed and is included in Identity Broker v5.0.5 RC1. Are you able to upgrade to this version?

Applied v5.0.5 RC1 and group membership is now being cleared as expected.