From 5a58ea580912f450feee8c0c12ca7a8735cfce13 Mon Sep 17 00:00:00 2001 From: Oliver Gorwits Date: Mon, 10 Feb 2014 13:49:57 +0000 Subject: [PATCH] suggest alternative workaround for no MD5/TCP auth --- Netdisco/lib/App/Netdisco/Manual/Deployment.pod | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/Netdisco/lib/App/Netdisco/Manual/Deployment.pod b/Netdisco/lib/App/Netdisco/Manual/Deployment.pod index c509821d..3c5a68c9 100644 --- a/Netdisco/lib/App/Netdisco/Manual/Deployment.pod +++ b/Netdisco/lib/App/Netdisco/Manual/Deployment.pod @@ -5,8 +5,15 @@ App::Netdisco::Manual::Deployment - Tips and Tricks for Deployment =head1 Enable MD5 authentication to PostgreSQL Some installations of PostgreSQL don't have MD5 authentication enabled by -default. You should enable this by adding the following to your system's -"C" file (and restarting the database service): +default, which blocks database connections with the default Netdisco +configuration. + +If your database and Netdisco are on the same system, then the easiest +solution is to comment out the "C" line in your C file. + +Alternatively, reconfigure PostgreSQL to permit MD5 auth for TCP connections +by adding the following to your system's "C" file (and restarting +the database service): # TYPE DATABASE USER ADDRESS METHOD host all all 127.0.0.1/32 md5