Google Apps Directory Sync LDAP port 389

Posted on 2010-08-20
Last Modified: 2012-08-13
I'm configuring Google Apps Directory Sync and forward port 389 to my Active Directory server.

It works. But is this a security risk?

If yes, what are the steps/requirements for using LDAP+SSL for the connection?

Question by:TANGLAD
  • 3
  • 3

Accepted Solution

Paul Tozer earned 500 total points
ID: 33483371
The issue would be that the password is sent as plain text so a packet sniffer could potentially get the password. Depending on how much priviliges you give the account used to read the LDAP, could be a security risk.

See if you want to change your LDAP to use SSL, plus change your connection on Directory Sync to use port 636 instead of 389

Personally mine is set to use 389, and as our domain controller has outbound internet access I run the directory sync from it, negating the issue.

Author Comment

ID: 33483386
I run the directory sync on the domain controller as well and I have forwarded port 389 to the dc.
Is that a risk?

Expert Comment

by:Paul Tozer
ID: 33483434
how do you mean you have forwarded port 389 on the dc.

all you need to do is set it as attached image, changing your base DN and authorised user

I can't see any security risk as it is done locally (so no network sniffing), and port 389 is open anyhow
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.


Author Comment

ID: 33483491
I did the forward in the firewall

Expert Comment

by:Paul Tozer
ID: 33483791
Don't do that, there is no need. That is a security risk

The directory sync reads the LDAP details locally and then uploads the information to Google/Postini through HTTP/S

Author Closing Comment

ID: 33487284
Great. Thanks

Featured Post

Why are Office 365 signatures so complicated?

Trying to setup transport rules for Office 365 email signatures and can’t quite figure it out? Having to test the signature over and over? Make things simple by using Exclaimer Cloud - Signatures for Office 365.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
exchange, scripts 30 74
Exchange 2016 - What permissions does a user need in order to create Distribution Groups? 3 36
Office 365 & Microsoft Azure 8 48
exchange, outlook 8 52
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

937 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now