When I restart the dirsrv-admin process on my 389 server, any attempt to login
to the 389-console with my LDAP user ID fails with the following message:
"Cannot logon because of an incorrect User ID, Incorrect Password or Directory
problem
HttpException:
Response: HTTP/1.1 401 Authorization Requi
On RedHat Linux I did this by adding an entry to /etc/security/access.conf to
allow certain groups to login.
Here's what mine looks like:
# grep -v ^# /etc/security/access.conf
+ : safull sagroup2 : ALL
- : saldap : ALL
Safull is the group that is allowed access to that server, I also put ever
Ok so to stop updates just don't let the clients through the firewall. To
allow updates I'd investigate the ChainOnUpdate method. Thanks Rich
From: Rich Megginson [mailto:rmegg...@redhat.com]
Sent: Thursday, February 09, 2012 11:38 AM
To: Groten, Ryan
Cc: General discussion list f
e 389 Directory server project.
Cc: Groten, Ryan
Subject: Re: [389-users] How do read-only consumers work?
On 02/09/2012 11:24 AM, Groten, Ryan wrote:
Hi all,
I'm testing out setting up 2 read-only consumers (each matches 1 of 2
multi-masters). Seems to be working fine, but I'm ju
Hi all,
I'm testing out setting up 2 read-only consumers (each matches 1 of 2
multi-masters). Seems to be working fine, but I'm just trying to wrap my head
around what's happening when changes are made:
1. Have 2 multi-master Directory Servers (1.2.9.9) setup and running
2. Creat
From: Rich Megginson [mailto:rmegg...@redhat.com]
Sent: Tuesday, January 03, 2012 4:18 PM
To: Groten, Ryan
Cc: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] bak2db restore got stuck in infinite loop
On 01/03/2012 03:50 PM, Groten, Ryan wrote:
From
Hi everyone,
In my environment I have a total of 4 directory servers, 2 multi-masters in
production (ServerA, ServerB) and 2 multi-masters to test with (ServerC,
ServerD). Basically here's what I did:
1. Took a backup of one of the production directory servers, ServerA
2. Copied
