I have done many of 389 ldap server setups.
Have a new install, and I can't get for the life of me able to get the
admin console to connect to the server.
Message i get is
[Tue Sep 21 14:55:44.279828 2021] [:notice] [pid 1337:tid 140593598555904]
[client xx.xx.xx.xxx:61796] admserv_check_authz()
Why is a one letter wildcard search not hitting the index?...yet if you add
two or more letters to the wildcard, the index is used. Yes cn does have 3
indexes on it.
Example
26/Feb/2021:16:33:51.189998029 -0600] - NOTICE - ldbm_back_search -
Unindexed search: search base="cn=users,o=Xx,O=Xxxx
Thanks for the great explanation William!
On Thu, Dec 19, 2019 at 9:16 AM Alberto Viana wrote:
> William,
>
> It's clear to me.
>
> I will try centos8 :)
>
> Thanks.
>
> Alberto VIana
>
> On Thu, Dec 19, 2019 at 2:50 AM William Brown wrote:
>
>>
>>
>> > On 19 Dec 2019, at 08:09, Alberto Viana
interesting;
so I did the following, and it's up and running now
yum remove 389*
yum install 389-ds-base
cd /etc/dirsrv/config/
yum install 389*
On Tue, Aug 20, 2019 at 8:24 PM Chase Miller wrote:
> yum whatprovides '/etc/dirsrv/config/certmap.conf'
>
> Loade
IE remove-ds.pl. It's probably wise to also yum reinstall
> 389-ds-base and check /etc/dirsrv to ensure config was created.
>
> > On 21 Aug 2019, at 10:13, Chase Miller wrote:
> >
> > pwd
> > /etc/dirsrv
> > [root@xx dirsrv]# ls -l
> > total
pwd
/etc/dirsrv
[root@xx dirsrv]# ls -l
total 0
drwxrwx--- 3 dirsrv dirsrv 61 Aug 19 13:41 slapd-xxx
On Tue, Aug 20, 2019 at 6:58 PM William Brown wrote:
>
>
> > On 20 Aug 2019, at 23:27, Chase Miller wrote:
> >
> > ss -tlnp
> > State Re
'/tmp/setupwT17yV.log'
On Mon, Aug 19, 2019 at 7:41 PM William Brown wrote:
>
>
> > On 20 Aug 2019, at 01:54, Chase Miller wrote:
> >
> > Hello,
> >
> > I have a fresh install of Centos 7.
> > (this is not my first install of Dire
Hello,
I have a fresh install of Centos 7.
(this is not my first install of Directory Server, btw)
Followed this article:
https://webhostinggeeks.com/howto/setup-389-directory-server-on-centos-7/
cat setupV6AAJP.log
[19/08/19:08:49:28] - [Setup] Info This program will set up the 389
Directory
Hello,
I'm trying to get the lastlogon timestamp populated when users login/bind.
I have enabled the account policy plugin, what else do I need to do?
regards,
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email
Hello All,
I deleted my root suffix, and now, in the admin console, I can't recreate
the suffix, tells me it already exists.
Any ideas what file I can go edit to clean up any orphaned references to it
of it?
I have recycled the server, I have done a restore from backup.
cm
--
389 users mailing
Hello;
After enabling the Account Policy Plugin, the lastlogintime is still not
being populated with a timestamp.
chase
On Fri, May 8, 2015 at 8:58 AM, Mark Reynolds wrote:
>
>
> On 05/08/2015 09:51 AM, Chase Miller wrote:
>
> Hello 389 Group,
>
> Is there an object c
Hello 389 Group,
Is there an object class/attribute that I can add to a user's entry that
will capture their last authenticated time stamp. I want to capture this
so I can go delete users that have not authenticated after so many days.
Chase
--
389 users mailing list
389-users@lists.fedoraprojec
Hello,
So I have a development ldap server up and running with all of my custom
object classes and attributes. Now, is there a way to export these and
import them on my new production boxes, so I don't have to re-create all of
them.
Chase
--
389 users mailing list
389-users@lists.fedoraproject.o
good thing / bad thing
So I have a fedora directory server version 1.1.0, build date of 2007, and
now I'm trying to migrate to a new server, so I have installed the
latest/greatest. I'm having issues on my ldif imports, it's blowing up on
Boolean string, yet if I change it to Directory string, it
userPasswordNeverExpires: false
On Tue, Sep 2, 2014 at 9:57 AM, Rob Crittenden wrote:
> Chase Miller wrote:
> > Hello,
> >
> > I have an old fedora directory server, and I'm migrating it to a new
> > server, and on the new server, I have installed the latest
Hello,
I have an old fedora directory server, and I'm migrating it to a new
server, and on the new server, I have installed the latest version.
I had a custom attribute with a Boolean data type in the old one, and now,
when I try to ldif import into the new server, I receive an error "value #0
in
Is broke
Sent from my iPhone
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
17 matches
Mail list logo
