I set up the password policies on the 389 directory server, and now it
happens that when I try to log in as admin, it says "Password
How it's possible? The admin user is the one setup for management with
the 389 console ....
ICQ #: 9103167
MSN Messenger: astraroth(a)email.it
Yahoo & Skype: gioachino_bartolotta
I set up a host with centos 5.6 and 389-ds 1.1.3 for testing purposes.
On startup of the directory, it states:
[08/Jul/2011:15:36:44 +0200] - 389-Directory/1.2.2 B2009.237.2054
[08/Jul/2011:15:36:46 +0200] - slapd started. Listening on All
Interfaces port 389 for LDAP requests
[08/Jul/2011:15:36:47 +0200] - Listening on All Interfaces port 636 for
on that host I can see ldap and ldapssl ports open, and p.ex.
389-console shows reasonable stuff.
However, on other hosts I cannot, queries on the directory fail - Seems
to me like the server only listens on the loopback interface.
Any Ideas about this?
I have setup my 389 directory server (in fact it's a centos-ds) and
now I need to allow my users to change their passwordss. The problem
is that most of my users do not have a shell script and/or I do not
trust their clients.
I need to provide some web page so that thay can do it. Does anyone
has any sugestion?
Our setup has one location with a pair of multi-masters (call it "location
A") and another location with a pair of consumers (call it "location B".
I'd like to "switch directions" between the locations so the servers in
"location B" will be multi-masters between themselves and the servers in
location "A" will be "downgraded" to simple consumers.
As far as I understand the documentation, this might be possible by adding
the "missing replication agreements (i.e. tell the "location B" servers to
become multi-masters and tell the current multi-masters in "location A" to
also accept updates from "location B").
Effectively, this should convert the current two-way multi-master cluster in
"location A" into a four-way multi-master cluster across "location A" and
"location B". Once this is done I expect that I can "downgrade" the
"location A" servers to simple consumers by removing the current replication
agreement they have (or even replace them with a new installation altogether
if that's not possible).
Am I correct or is it more complicated than that?
I've got a directory server and DSGW running.
Mail server, openvpn server and samba share use ldap authentication against
this directory server. Users change their passwords in DSGW.
The mailserver and openvpn use SSHA hash in "userpassword" field, but samba
uses NT hash and LM hash in "sambantpassword" and "sambalmpassword" fields
How can I make "userpassword" , "sambantpassword" and "sambalmpassword"
fields change synchronously when users change their passwords in DSGW?
As I can understand, there is no already written 389-DS-plugin for
Moreover, it seems to me that such issues as mine are often solved on the
Am I right?
So should I change
is responsible for password change in DSGW? Does it seem to be useful
Looking forward to your prompt repy.