[389-users] Re: DNA plugin not working

On 4/17/20 5:19 PM, CHAMBERLAIN James wrote: Hi all, Thank you all for your help. I’ve gotten DNA working. I’ll be doing some further work to convince myself that I understand exactly what I did that got it working and can replicate it; but in the meantime, I had a question or two. Do I

[389-users] Re: DNA plugin not working

Hi all, Thank you all for your help. I’ve gotten DNA working. I’ll be doing some further work to convince myself that I understand exactly what I did that got it working and can replicate it; but in the meantime, I had a question or two. Do I correctly understand RHDS 11 Administration

[389-users] Re: 389-ds on Leap 15.1 - teething pains - it is running (with some issues) - but I still cannot test authentication

Hi, On 17.04.20 at 18:01 Clayvahn Hunt wrote: > I have done as you suggest (see dsrc contents below), restarted the instance, > then (note: ldaps://ent-a.aeho.lan): > LDAPTLS_CACERT=/etc/dirsrv/slapd-localhost/ca.crt ldapwhoami -v -H > ldaps://ent-a.aeho.lan -D

[389-users] Re: replication problems

Hi Guys, I build my own packages (from source), here's the info: 389-ds-base-1.4.2.8-20200414gitfae920fc8.el8.x86_64.rpm 389-ds-base-debuginfo-1.4.2.8-20200414gitfae920fc8.el8.x86_64.rpm python3-lib389-1.4.2.8-20200414gitfae920fc8.el8.noarch.rpm I'm running in centos8. Here's what I could

[389-users] Re: 389-ds on Leap 15.1 - teething pains - it is running (with some issues) - but I still cannot test authentication

Each section [] refers to an instance on your local system.  For example I have an instance named localhost.  It can be found on the FS under /etc/disrv/slapd-locahost, but I could have named the instance anything, like:  slapd-MARK (/etc/dirsrv/slapd-MARK).  In the second case I would use the

[389-users] Re: 389-ds on Leap 15.1 - teething pains - it is running (with some issues) - but I still cannot test authentication

Also, W. Brown gave me this hint: "There can be many sections in the dsrc though, and they can be named differently to your instances if you want. I wrote most of that code so I can explain further if you want. But you could do something like: [localhost] uri =

[389-users] Announcing 389 Directory Server 1.4.4.0

389 Directory Server 1.4.4.0 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.4.0 Fedora packages are available on Rawhide (Fedora 33). https://koji.fedoraproject.org/koji/taskinfo?taskID=43472534

[389-users] Announcing 389 Directory Server 1.4.3.6

389 Directory Server 1.4.3.6 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.3.6 Fedora packages are available on Fedora 32. https://koji.fedoraproject.org/koji/taskinfo?taskID=43473813

[389-users] Announcing 389 Directory Server 1.4.2.12

389 Directory Server 1.4.2.12 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.2.12 Fedora packages are available on Fedora 31. https://koji.fedoraproject.org/koji/taskinfo?taskID=43476746 Bodhi

[389-users] Announcing 389 Directory Server 1.4.1.18

389 Directory Server 1.4.1.18 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.1.18 Fedora packages are available on Fedora 30. https://koji.fedoraproject.org/koji/taskinfo?taskID=43477252 Bodhi

[389-users] Re: 389-ds on Leap 15.1 - teething pains - it is running (with some issues) - but I still cannot test authentication

> Hmm, for creation of new users I have to add the full thing, but for "user > list" > or "user get" I can omit the basedn. I've just checked again after putting the dsrc file back to the way it's supposed to be and I *still* need to include the basedn for my dsidm calls. That suggests to me an

[389-users] Restricting access to the LDAP server

Hi all, while setting up my demo server I found that I am completely lacking knowledge in that respect. I found those two and will work through them. https://directory.fedoraproject.org/docs/389ds/howto/howto-accesscontrol.html

[389-users] Re: 389-ds on Leap 15.1 - teething pains - it is running (with some issues) - but I still cannot test authentication

On 17.04.20 at 15:59 Clayvahn Hunt wrote: > First, I need to say that the documentation for Leap 15.1, although good, is > not (IMO) as good as the documentation at: > http://www.port389.org/docs/389ds/howto/quickstart.html Seconded. For some reason there are other examples, introducing some

[389-users] Re: 389-ds on Leap 15.1 - teething pains - it is running (with some issues) - but I still cannot test authentication

And *this* line would be helpful in the openSUSE docs: For now, we recommend you use the local version with ldapi ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] 389-ds on Leap 15.1 - teething pains - it is running (with some issues) - but I still cannot test authentication

All, I have (so far) been helped by two awesome folks (A. Stieger & W. Brown) to get this up & running. I have a *running* 389 server (I manually added the 'ensure_list_str' variable that was missing to setup.py (thanks W. Brown)), but I *still* cannot test authentication (more on this later).

[389-users] Re: Where to report issues with the documentation on port389.org / directory.fedoraproject.org/docs/?

On 17.04.20 at 14:43 Mark Reynolds wrote: > All your current PR's have been merged!  Keep them coming ;-) Thanks, that was quick! Sure, will do so! Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: ka...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 /

[389-users] Re: Where to report issues with the documentation on port389.org / directory.fedoraproject.org/docs/?

On 4/17/20 2:25 AM, Johannes Kastl wrote: Hi Mark, thanks for the quick answer. On 16.04.20 at 23:06 Mark Reynolds wrote: Where to report those issues? Is there a pagure/github/gitlab/... repo for the documentation, so I could just open a pull request? You signed off too quickly from IRC

[389-users] Exporting to LDIF

Hi again, I found several links on how to export from 389 to LDIF. Most of them seem to be outdated? Or maybe this is just because of different packaging on RedHat compared to my openSUSE test machine. It boils down to "db2ldif" not being present on my machine.

[389-users] SSSD Howto: Why not use pam-config on SUSE/openSUSE?

Hi, uis there a special reason why the SSSD Howto https://www.port389.org/docs/389ds/howto/howto-sssd.html does not use "pam-config -a -sss" on SUSE/openSUSE? Instead if manually tweaking (and breaking) the files, this does what is needed in the proper way. If there isn't, I would create a PR

[389-users] Re: Where to report issues with the documentation on port389.org / directory.fedoraproject.org/docs/?

Hi William, On 17.04.20 at 08:45 William Brown wrote: > I work with the doc authors for those, so I can help you get them resolved if > you have issues :) I filed boo#1169703 yesterday. Not sure where this documentation is kept. As it seems to be shared between SUSE and openSUSE I guess

[389-users] Quickstart documentation: SSSD setup needs "memberOf" plugin enabled

Hi guys, the quickstart documentation (which is a very nice piece of documentation) does setup the memberOf plugin. http://www.port389.org/docs/389ds/howto/quickstart.html However the SSSD part does not mention that you need to have that plugin enabled on the server, otherwise you will not get a

[389-users] Re: Where to report issues with the documentation on port389.org / directory.fedoraproject.org/docs/?

> On 17 Apr 2020, at 16:31, Johannes Kastl wrote: > > Hi William, > > On 17.04.20 at 01:09 William Brown wrote: >>> On 17 Apr 2020, at 05:55, Johannes Kastl wrote: >>> But of course I found some issues, that I would like to address. >> >> You can report them here too so we can discuss them