Troubleshooting Incorrect Password Notification for Google G-Suite Integration and SEG v2
Question
An administrator has successfully configured the Google G-Suite integration with SEG v2 and password provision for all of the users.
However, after a period of time, users receive a wrong password notification when trying to sync emails.
What can cause this issue? (Choose two.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.AB.
https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1811/VMware%20Workspace%20ONE%20UEM%20Google%20Sync%20Integration%The issue of users receiving a wrong password notification when trying to sync emails in the Google G-Suite integration with SEG v2 and password provision can be caused by a number of factors. The two most likely causes of this issue are:
The Google Apps Directory Sync (GADS) is enabled GADS is a tool that synchronizes data between a company's Active Directory and their Google Workspace domain. If GADS is enabled and it is configured to manage user passwords, it can overwrite the password provision set up by the Workspace ONE UEM, causing users to receive a wrong password notification.
The service account certificate is not valid and needs to be updated on the G-Suite admin interface and uploaded to Workspace ONE UEM The service account certificate is used by the SEG v2 to authenticate with the Google Workspace APIs. If the certificate is not valid or has expired, the SEG v2 will not be able to authenticate with the Google Workspace APIs, which can cause the wrong password notification issue. In this case, the service account certificate needs to be updated on the G-Suite admin interface and uploaded to Workspace ONE UEM.
Other potential causes of the wrong password notification issue include:
The Google Apps Password Sync (GAPS) is enabled: GAPS is a tool that synchronizes user passwords from a company's Active Directory to their Google Workspace domain. If GAPS is enabled and it is configured to manage user passwords, it can overwrite the password provision set up by the Workspace ONE UEM, causing users to receive a wrong password notification.
SEG is not listening to port 443: SEG v2 requires port 443 to be open for communication with the Google Workspace APIs. If SEG v2 is not listening to port 443, it will not be able to authenticate with the Google Workspace APIs, which can cause the wrong password notification issue.
IP Whitelist is disabled in the Google Admin Console: The IP Whitelist is used to restrict access to the Google Workspace APIs to specific IP addresses. If the IP Whitelist is disabled, unauthorized access to the Google Workspace APIs may occur, causing the wrong password notification issue.
In summary, the two most likely causes of the wrong password notification issue in the Google G-Suite integration with SEG v2 and password provision are the Google Apps Directory Sync (GADS) being enabled and the service account certificate being invalid or expired. Other potential causes include the Google Apps Password Sync (GAPS) being enabled, SEG not listening to port 443, and IP Whitelist being disabled in the Google Admin Console.
