BIND (DNS)
by Fernando Fuentes
Is there a plugin or a default schema for BIND (named) on Fedora389? Or
do I have to import the included schema with bind9?
Thanks!
Regards,
-
4 years, 7 months
Reminder of 389-admin, console, and webapp deprecation & removal
by Mark Reynolds
This is just a reminder that the old Java Console and Admin Server have
been deprecated, and these packages will be removed from future versions
of the product. Starting in Fedora 31, RHEL 8, CentOS 8, and SUSE 15
there will no longer be a Java Console (389-console), Admin Express, or
Directory Server Gateway.
Instead, we have a new web UI that is a Cockpit plugin (cockpit-389-ds)
[1]. The new Cockpit UI is solely for administering and configuring the
server. As previously announced there will not be an LDAP browser as
part of the new UI. So User & Group management needs to be done via the
new CLI tools or via free products like Apache Directory Studio. We do
plan to add a simple LDAP browser in the near future, but that work has
not begun yet.
Sorry for any inconvenience this presents, but we needed to move off of
the old java technology so we did not get stuck in another 8 year
support cycle. We hope you like the new UI and CLI tools, and we will
continue to improve them with each release. Feel free to file tickets
for RFE's and bugs here: https://pagure.io/389-ds-base/new_issue
Sincerely,
389 Directory Server Development Team
[1] https://cockpit-project.org/
--
389 Directory Server Development Team
4 years, 7 months
Windows Sync Agreement issue
by DaV
Hi all,
I'm using a new 389 directory server on CentOS 7.6 with 389-ds-base.x86_64 (1.3.8.4-15.el7), and I want to sync user and password from Windows 2016 to 389ds one way.
The Synchronization Agreement like this:
DS Host: 389ds:389
Windows Host: dc01.example.com:389
DS Subtree: ou=Users,dc=example,dc=com
Windows Subtree: OU=Accounts, DC=example,DC=com
Replicated subtree: dc=example,dc=com
Here is my question:
The sync agreement can only sync top-level OU=Accounts, DC=example, DC=com from Win2016 to 389ds server.
In fact, I have
ou=ou1,ou=accounts,dc=example,dc=com
ou=ou2,ou=accounts,dc=example,dc=com
on Win2016 server.
I want the sync agreement can sync not only the top-level but also the child ou.
This is the error log for your reference. Thanks!
> [20/Aug/2019:07:58:40.307031692 +0800] - ERR - NSMMReplicationPlugin - windows sync - windows_tot_run - Beginning total update of replica "agmt="cn=389ds" (tc-dc-2:389)".
> [20/Aug/2019:07:58:40.309113230 +0800] - INFO - slapd_daemon - slapd started. Listening on All Interfaces port 389 for LDAP requests
> [20/Aug/2019:08:34:21.730939271 +0800] - WARN - NSMMReplicationPlugin - windows sync - windows_inc_run - agmt="cn=389ds" (tc-dc-2:389): Replica has no update vector. It has never been initialized.
> [20/Aug/2019:08:34:21.733526550 +0800] - WARN - NSMMReplicationPlugin - windows sync - windows_inc_run - agmt="cn=389ds" (tc-dc-2:389): Replica has no update vector. It has never been initialized.
> [20/Aug/2019:08:34:24.735819391 +0800] - WARN - NSMMReplicationPlugin - windows sync - windows_inc_run - agmt="cn=389ds" (tc-dc-2:389): Replica has no update vector. It has never been initialized.
> [20/Aug/2019:08:34:27.738228528 +0800] - WARN - NSMMReplicationPlugin - windows sync - windows_inc_run - agmt="cn=389ds" (tc-dc-2:389): Replica has no update vector. It has never been initialized.
> [20/Aug/2019:08:34:30.873896680 +0800] - ERR - NSMMReplicationPlugin - windows sync - windows_tot_run - Beginning total update of replica "agmt="cn=389ds" (tc-dc-2:389)".
> [20/Aug/2019:08:34:33.170822223 +0800] - ERR - NSMMReplicationPlugin - windows sync - windows_tot_run - Finished total update of replica "agmt="cn=389ds" (tc-dc-2:389)". Sent 5 entries.
> [20/Aug/2019:08:34:33.186359842 +0800] - ERR - NSMMReplicationPlugin - windows sync - bind_and_check_pwp - agmt="cn=389ds" (tc-dc-2:389): Replication bind with SIMPLE auth resumed
> [20/Aug/2019:08:47:30.032935119 +0800] - ERR - NSMMReplicationPlugin - windows sync - windows_tot_run - Beginning total update of replica "agmt="cn=389ds" (tc-dc-2:389)".
> [20/Aug/2019:08:47:31.035850854 +0800] - ERR - NSMMReplicationPlugin - windows sync - windows_tot_run - Finished total update of replica "agmt="cn=389ds" (tc-dc-2:389)". Sent 5 entries.
> [20/Aug/2019:08:47:31.051614890 +0800] - ERR - NSMMReplicationPlugin - windows sync - bind_and_check_pwp - agmt="cn=389ds" (tc-dc-2:389): Replication bind with SIMPLE auth resumed
> [20/Aug/2019:08:50:59.533268105 +0800] - WARN - NSMMReplicationPlugin - prot_stop - Incremental protocol for replica "agmt="cn=389ds" (tc-dc-2:389)" did not shut down properly.
> [20/Aug/2019:09:01:00.155477769 +0800] - WARN - NSMMReplicationPlugin - prot_stop - Total protocol for replica "agmt="cn=389ds" (tc-dc-2:389)" did not shut down properly.
Sincerely,
--
DaV
4 years, 7 months
