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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 CLI as follows:

# dsidm MARK user list    (You can optionally use the "slapd-" prefix for clarity:    dsidm slapd-MARK user list)

So in my .dsrc file I would need a section like:

[MARK]
uri: ldapi://%%2fvar%%2frun%%2fslapd-MARK.socket
...


So each section describes a local instance.  I'm not sure you can create different profiles like what you are doing below.  William knows the .dsrc stuff better than I do though so he might have additional comments when he gets online.

Note - I'm not sure what version you are, but in older versions the section name must match how to type it on the CLI.   So if .dsrc contains [MARK], then you MUST use:  "dsidm MARK ...".  If you defined the section name as [slapd-MARK] in .dsrc, then you must use:  "dsidm slapd-MARK ...".  This has been fixed in newer versions where you can interchange the "slapd-" anyway you want and it will still find the correct section in .dsrc.

HTH,
Mark

On 4/17/20 12:27 PM, Clayvahn Hunt wrote:
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 = ldapi://%%2fvar%%2frun%%2fslapd-localhost.socket

[localhost-ldaps]
uri =
ldaps://localhost
"

I have done this (see other entries here) - but after reading this *many, many times* I do have a question. The suggestion (at least to me) suggests that I'd need multiple instances ("named differently to your instances if you want") - so that means I'd have more than one LDAP instance - one that I'd administer locally ([localhost] via ldapi) and one instance ([localhost-ldaps]) that I'd administer via ldaps. How would I ensure both instances used the same database? I don't want to have to create more work for myself.

Can anyone offer any clarification of how I might make this configuration work with least headache?

Thanks in advance


_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx

--

389 Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux