We have been working this problem for two weeks debugging. We have 389-ds
running and multi-master with 3 RHEL6 servers and a RHEL5. The RHEL5 ldap
clients authenticate correctly to the RHEL6 389-ds directory server and
with 'id' command can see all groups a user belongs too.
The same command
On Tue, Oct 22, 2013 at 9:51 AM, harry.dev...@faa.gov wrote:
We have been working this problem for two weeks debugging. We have 389-ds
running and multi-master with 3 RHEL6 servers and a RHEL5. The RHEL5 ldap
clients authenticate correctly to the RHEL6 389-ds directory server and
with 'id'
We tried that and, sadly, it made no difference. In fact, we get LESS
information that before. It appears as though we get the main group, and
it does not know how to dig further to get the sub-groups and group
members. Also, we found that our ldap_group_member is called uniqueMember
and
Existing entries are not added automatically when enabling the plugin, you
have to either run the fixup-memberof.pl script (if it works for you - it
never did anything for us), or you have to make a change to each
pre-existing user to trigger the memberOf updating. The easiest way to do
that is to
Hello,
Translate text or webpage
Could anyone help me??
I configured in the pacemaker ClusterMON but get no email. Already tested the
email from the command line and all is right.
I am sending configuration I did. What's wrong??
I will deploy the environment this weekend and would like
On 10/22/2013 11:44 AM, Jonathan Vaughn wrote:
That was exactly the way we ran it, per that documentation, but it
didn't appear to do anything.
You can check the /var/log/dirsrv/slapd-INST/errors log file to see if
it ran and if there were any errors.
So, I figured out that just
