I just followed that and made the changes, restarted the server, and
logged in with user account. I logged in fine, but if I try to do an
ldapsearch and search for lastLoginTime, I get nothing back. I don't see
that attribute in that user's Advanced Properties page either. So, I
guess its ba
On 07/30/2013 08:09 AM, Kyle Johnson wrote:
I have found this bug
(https://bugzilla.redhat.com/show_bug.cgi?id=514955), with a patch
that appears to have been applied back in 2009.
Would that patch have made it into 389?
What version of 389-ds-base are you using?
Kyle
On 2013-07-29 15:2
Sorry, I should know better. 389-ds-base-1.2.11.15-12.el6_4.x86_64
On 2013-07-30 10:38, Rich Megginson wrote:
On 07/30/2013 08:09 AM, Kyle Johnson wrote:
I have found this bug
(https://bugzilla.redhat.com/show_bug.cgi?id=514955), with a patch
that appears to have been applied back in 2009.
On 07/30/2013 08:41 AM, Kyle Johnson wrote:
Sorry, I should know better. 389-ds-base-1.2.11.15-12.el6_4.x86_64
Then yes, it has that patch.
On 2013-07-30 10:38, Rich Megginson wrote:
On 07/30/2013 08:09 AM, Kyle Johnson wrote:
I have found this bug
(https://bugzilla.redhat.com/show_bug.cgi
If it has the patch, what would be causing my dnanextvalue fields to not
be in sync? They're using the local value of the dnanextvalue, and when
adding a new user, the UID and GID are at the beginning of the local
value instead of matching the value on the other server.
On 2013-07-30 10:42, R
On 07/30/2013 07:26 AM, harry.dev...@faa.gov wrote:
I just followed that and made the changes, restarted the server, and
logged in with user account. I logged in fine, but if I try to do an
ldapsearch and search for lastLoginTime, I get nothing back. I don't
see that attribute in that user'
On 07/30/2013 10:19 AM, Kyle Johnson wrote:
Each server does have the same range, yes,
Why?
however the first server was configured about a month before the
second was even stood up. Here is the ldif that I used on the new
server; the same ldif was used on the original server:
dn: cn=UID
Each server does have the same range, yes, however the first server was
configured about a month before the second was even stood up. Here is
the ldif that I used on the new server; the same ldif was used on the
original server:
dn: cn=UID numbers,cn=Distributed Numeric Assignment
Plugin,cn=
Sorry, I think I'm following now. Instead of syncing the dnanextvalue
between servers, each server should have a range that doesn't overlap
with the other.
On 2013-07-30 12:36, Rich Megginson wrote:
On 07/30/2013 10:19 AM, Kyle Johnson wrote:
Each server does have the same range, yes,
Why?
