diff --git a/docs/en_US/images/server_connection.png b/docs/en_US/images/server_connection.png
index 8f61bde00e633a7bc7afd53dca017d6ccb52fd5d..b2cd3e403428227e95589ac939992ad416e763c4 100644
GIT binary patch
diff --git a/docs/en_US/kerberos.rst b/docs/en_US/kerberos.rst
index 58ccbef0c..61b800a90 100644
--- a/docs/en_US/kerberos.rst
+++ b/docs/en_US/kerberos.rst
@@ -67,3 +67,13 @@ You need to do the browser settings on the client machine to use the *Spnego/Ker
     .. code-block:: text
 
        google-chrome --auth-server-whitelist = "hostname/domain"
+
+
+PostgreSQL Server settings to configure Kerberos Authentication
+===============================================================
+* To connect the PostgreSQL server with Kerberos authentication, the GSSAPI support has to be enabled when PostgreSQL is built and necessary configurations has to be in place.
+
+* In pgAdmin, you need to enable the Keberos authentication for the PostgreSQL server by setting "Kerberos authentication" flag to True in the Server dialog.
+  Once it is enabeled, pgAdmin will not prompt for the password and try to connect PostgreSQL server via Kerberos.
+
+* Note that, you have to login into pgAdmin with Kerberos authnetication, to connect PostgreSQL via Kerberos.
diff --git a/docs/en_US/server_dialog.rst b/docs/en_US/server_dialog.rst
index e9c010f0b..68f0a1a52 100644
--- a/docs/en_US/server_dialog.rst
+++ b/docs/en_US/server_dialog.rst
@@ -62,6 +62,8 @@ Use the fields in the *Connection* tab to configure a connection:
   installed on that database.
 * Use the *Username* field to specify the name of a role that will be used when
   authenticating with the server.
+* When *Kerberos authentication?* is set to *True*, pgAdmin will try to connect
+  the PostgreSQL server via Kerberos authentication.
 * Use the *Password* field to provide a password that will be supplied when
   authenticating with the server.
 * Check the box next to *Save password?* to instruct pgAdmin to save the
