[389-users] Announcing 389 Directory Server 1.4.2.11

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

[389-users] Announcing 389 Directory Server 1.4.3.5

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

[389-users] Re: replication problems

On 3/31/20 1:36 PM, Alberto Viana wrote: Hey Guys, 389-Directory/1.4.2.8 389 (master) <=> 389 (master) In a master to master replication, start to see this error : [31/Mar/2020:17:30:52.610637150 +] - WARN - NSMMReplicationPlugin - replica_check_for_data_reload -

[389-users] Re: Scripted letsencrypt certificate for 389-ds

On 3/30/20 5:54 PM, William Brown wrote: On 31 Mar 2020, at 01:14, Laurent GUERBY wrote: On Mon, 2020-03-30 at 09:16 +0200, Laurent GUERBY wrote: On Sun, 2020-03-29 at 20:15 -0400, Mark Reynolds wrote: Second, 1.4.0 is dead and has not been maintained in a very long time so the UI

[389-users] Re: Scripted letsencrypt certificate for 389-ds

On 3/29/20 4:53 PM, William Brown wrote: On 30 Mar 2020, at 06:29, Laurent GUERBY wrote: Hi, I installed 389-ds 1.4.0.21-1 on a debian 10 system. When I use cockpit in 389-ds tab I get "{'desc': 'Inappropriate authentication', 'info': 'SASL EXTERNAL bind requires an SSL connection'}" so I

[389-users] Announcing 389 Directory Server 1.4.2.9

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

[389-users] Announcing 389 Directory Server 1.4.1.16

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

[389-users] Announcing 389 Directory Server 1.4.3.4

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

[389-users] Re: Force use of secure connections

On 3/10/20 4:07 PM, Rob Crittenden wrote: Matthew Aguirre wrote: Is there a way to disable unsecured use of port 389?  I am using FreeIPA, so the client setup uses port 389 with TLS and that is fine, but I'd like to be able to not allow unsecured connections as much as possible. I was able to

[389-users] Re: Console Troubleshooting

Nelson, Yes I confirmed we have a faulty/corrupted build.  Still not sure how it happened, but it will be fixed in the next build.  I'm just waiting for a few more fixes to get committed then I will do new Fedora builds (and I'll send you the link to it) Regards, Mark On 3/7/20 9:39 PM,

[389-users] Re: Console Troubleshooting

On 3/7/20 9:39 PM, Nelson Bartley wrote: Hi Mark, Sorry for the delay in getting back to you. Mailing-list didn’t mail me….. I’ve attached the chrome console log to this email. The packages I’m using are Fedora 31: 389-ds-base.x86_64 1.4.2.8-3-fc31 Cockpit-389-ds.noarch

[389-users] Re: cockpit doubt, or rebuild Cockpit plugin

On 3/3/20 1:01 PM, Mark Reynolds wrote: On 3/3/20 12:28 PM, Alberto Viana wrote: Hi Guys, I'm testing some versions of 389 and I realise that in newer versions, cockpit stopped to work to me: /There is no 389-ds-base package installed on this system. Sorry there is nothing to manage

[389-users] Re: cockpit doubt

On 3/3/20 12:28 PM, Alberto Viana wrote: Hi Guys, I'm testing some versions of 389 and I realise that in newer versions, cockpit stopped to work to me: /There is no 389-ds-base package installed on this system. Sorry there is nothing to manage.../ In my case (due to internal reasons) we

[389-users] Re: Console Troubleshooting

On 3/2/20 9:53 AM, Nelson Bartley wrote: Good afternoon, I have fedora 31 cloud server installed on a local virtualbox. I have installed 389-ds and the 389-cockpit admin module. Using dscreate I created a local instance, and have successfully modified it with external tools. I have not

[389-users] Re: winsync password problems

turn it back "on" for winsync to send DS passwords to AD. We missed this, and I will make sure it gets documented right away in the Admin guide. Regards, Mark Thanks Alberto Viana On Fri, Feb 28, 2020 at 12:39 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote:

[389-users] Re: winsync password problems

l bring up again my old server, (and after that, rebuild my lab environment e try to figure it out). > > > > Right now, I'm testing with 3 different versions: > > 1.4.1.14 > > 1.4.3.2 > > 1.4.2.5 => This one with Fedora packages (not comp

[389-users] Re: 389ds and dual stack IPV4/6, also...

On 2/27/20 10:54 AM, N R wrote: I've been able to find what was wrong in my configuration, I had a typo in the /etc/hosts file. ^_^' Thank you a lot for your time and your precious advices. Glad you figured it out! Best regards, Nick Rand 2020-02-27 16:25 UTC+01:00, Mark Reynolds : On 2

[389-users] Re: 389ds and dual stack IPV4/6, also...

:::* LISTEN 1285/ns-slapd Why is the service always listening for IPV6 on port 636 whatever the parameter is set to? Then you want to use:  nsslapd-securelistenhost Best regards, Nick rand 2020-02-27 14:10 UTC+01:00, Mark Reynolds : On 2/27/20 8:03 AM, Mark Reynolds wrote: On 2/27/20 5

[389-users] Re: 389ds and dual stack IPV4/6, also...

On 2/27/20 8:03 AM, Mark Reynolds wrote: On 2/27/20 5:30 AM, N R wrote: Hello all, It's my first message on this list thanks in advance for your answers. I've configured a 389ds instance with ipv6 address and it's working great with it. How did you configure the instance exactly? What do

[389-users] Re: 389ds and dual stack IPV4/6

On 2/27/20 5:30 AM, N R wrote: Hello all, It's my first message on this list thanks in advance for your answers. I've configured a 389ds instance with ipv6 address and it's working great with it. I need for this instance to be reachable via ipv4 also but despite hours of research on the web

[389-users] Re: Console and Schema Attribute Errors

On 2/26/20 12:43 PM, Thad wrote: There are 2 LDIF files on the old server (01Common, 05RFC2247) that don't exist on the new server but no luck in finding that line. I went ahead and did a grep of the files in the schema directory on both servers and couldn't find that entry in either place.

[389-users] Re: winsync password problems

ame behavior, just the password is not sent from 389 to AD. In all versions, attributes are replicated(except password) from 389 to AD, and everything is working fine from AD to 389. Please let me know if need some more info. Thanks Alberto Viana On Wed, Jan 29, 2020 at 5:24 PM Mark Reynolds wrote:

[389-users] Announcing 389 Directory Server 1.4.1.15

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

[389-users] Re: winsync password problems

: cn=directory manager internalModifiersName: cn=directory manager Thanks On Wed, Jan 29, 2020 at 2:27 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote: On 1/29/20 12:17 PM, Alberto Viana wrote: Mark, Already did that twice hehehehe Do you think that's about config

[389-users] Re: winsync password problems

, 2020 at 12:35 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote: Alberto, Sorry I'm not sure what is wrong.  Please review the documentation and make sure you have everything setup correctly: https://access.redhat.com/documentation/en-us/red_hat_directory

[389-users] Re: winsync password problems

Alberto, Sorry I'm not sure what is wrong.  Please review the documentation and make sure you have everything setup correctly: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/managing_the_password_policy-synchronizing_passwords HTH, Mark

[389-users] Re: 389-admin

On 1/27/20 10:09 PM, William Brown wrote: On 26 Jan 2020, at 04:58, Giovanni Baruzzi wrote: Dear Ilia, I have similar problems. I am working under CentOS 7 and I would like to gather experience with the new Cockpit, but I found no packages and no information. How can we install it?

[389-users] Re: 389-admin

On 1/24/20 2:49 AM, Илья wrote: Hello! Planning to move from Centos 6 to Centos 8, but can not find any 389-Admin server packages. Are they at least exist? or Admin server is EOL project and there is another approach for 389 server management. I hardly can find any latest info about this

[389-users] Announcing 389 Directory Server 1.4.3.2

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

[389-users] Re: healthcheck problems

Viana On Thu, Jan 23, 2020 at 4:34 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote: On 1/23/20 1:17 PM, Alberto Viana wrote: Mark, I using python3-lib389-1.4.3.1-20200116gita08202a5b.el8.noarch python3.6 And still got the same error: DEBUG: [Errno

[389-users] Re: cockpit ui problem

On 1/23/20 1:31 PM, Alberto Viana wrote: 1. UI never shows password administrator field (always blank), even if is set: ~# dsconf instace_name config get passwordAdminDN passwordAdminDN: cn=GRP_SRV_PREHASHED_PASSWORD,ou=test,dc=my,dc=domain Also tried to setup via UI, but it's blank again

[389-users] Re: healthcheck problems

wrote: Mark, Thanks, I'm now building the packages as well. Alberto Viana On Mon, Jan 13, 2020 at 4:58 PM Mark Reynolds mailto:mreyno...@redhat.com>> wrote: On 1/13/20 2:56 PM, Alberto Viana wrote: Mark, Just to let you know, I'm cloning pagur

[389-users] Re: DB problems

dirsrv  10M Jan 17 12:19 log.03 drwx--. 2 dirsrv dirsrv 4.0K Jan 17 12:04 userroot Please tail the errors log, and try starting the server again. Please provide the entire error log output. Thanks, Mark Thanks On Fri, Jan 17, 2020 at 12:49 PM Mark Reynolds <mailto:mre

[389-users] Re: DB problems

/slapd-YOUR_INSTANCE/db/ Thanks, Mark Thanks On Fri, Jan 17, 2020 at 12:08 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote: On 1/17/20 9:55 AM, Alberto Viana wrote: Hi Guys, 389-Directory/1.4.3.1.20200116git4f9aafca9 Start to get this error: [17/Jan/2

[389-users] Re: DB problems

On 1/17/20 9:55 AM, Alberto Viana wrote: Hi Guys, 389-Directory/1.4.3.1.20200116git4f9aafca9 Start to get this error: [17/Jan/2020:11:49:56.436658541 -0300] - NOTICE - bdb_start - Detected Disorderly Shutdown last time Directory Server was running, recovering database. Anything else in

[389-users] Re: dsconf and dsctl bugs

On 1/16/20 2:25 PM, Alberto Viana wrote: Hi Guys, 389-Directory/1.4.3.1.20200116git4f9aafca9 B2020.016.1843 python3-lib389-1.4.3.1-20200116gita08202a5b.el8.noarch *dsconf*: If I try to create an instance got this error: DEBUG: name 'ensure_list_str' is not defined Traceback (most recent call

[389-users] Announcing 389 Directory Server 1.4.2.6

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

[389-users] Announcing 389 Directory Server 1.4.1.13

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

[389-users] Announcing 389 Directory Server 1.4.3

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

[389-users] Re: healthcheck problems

at 4:48 PM Alberto Viana <mailto:alberto...@gmail.com>> wrote: Mark, I'm installing it from source, to install lib389 I run: make lib389-install Am I missing something? Thanks Alberto Viana On Mon, Jan 13, 2020 at 4:36 PM Mark Reynolds mailto:mreyno...@r

[389-users] Re: healthcheck problems

-base/src/lib389 Am I missing something? Thanks Alberto Viana On Mon, Jan 13, 2020 at 4:36 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote: On 1/13/20 2:24 PM, Alberto Viana wrote: Mark, Here's: INFO: Checking DSEldif ... DEBUG: [Errno 2] No such file or

[389-users] Re: healthcheck problems

tory: '/etc/dirsrv/slapd-{instance_name}/dse.ldif' ERROR: Error: [Errno 2] No such file or directory: '/etc/dirsrv/slapd-{instance_name}/dse.ldif' Thanks. Alberto Viana On Mon, Jan 13, 2020 at 4:19 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote: On 1/13/20 2:07 PM, Alber

[389-users] Re: healthcheck problems

On 1/13/20 2:07 PM, Alberto Viana wrote: Hi Guys, In 389 version 1.4.2.4 healthcheck works fine: ~# dsconf RNP healthcheck Enter password for cn=Directory Manager on ldaps://localhost: Beginning lint report, this could take a while ... Checking Backends ... Checking Config ... Checking

[389-users] Re: Attribute encryption issue

On 1/10/20 6:48 PM, Iain Morgan wrote: Hi, , Yesterday, I ran up against an attribute encryption issue, and I'm looking for advice on how to debug and resolve the issue. For background, I have a pair of RHEL 7 servers in an MMR configuration. Let's call them host_A and host_B. Both are

[389-users] Re: Restore from Backup Fails

On 1/9/20 5:13 PM, Elena Rico wrote: Remove "-n userRoot" from the restore script, this "false option" was Removing this option from 'bak2db' fixed issue 1) however, 'bak2db.pl' still causes ns-slapd to crash. Did you remove "-n userRoot" from the perl script?  What was the exact CLI

[389-users] Re: Restore from Backup Fails

On 1/9/20 12:38 PM, Elena Rico wrote: Hello, We have noticed some inconsistent results while restoring from a backup. We are running the below script which takes backups nightly and then we use the 'bak2db' to restore. Version: 389-Directory/1.3.8.4 B2018.332.2046 We have noticed 2 issues:

[389-users] Re: Need Migration assist, please

On 1/7/20 9:09 AM, Jeffrey Westgate wrote: we are running "389-Directory/1.2.11.15 B2017.101.1347" on a Scientific Linux 6.9 VM.  We have a 2 server cluster running, and have for several years, with very little intervention required. we are wanting to move to RHEL8, and the latest (stable)

[389-users] Re: selinux doubts

quot; from the 389-ds-base/ directory? On Wed, Dec 18, 2019 at 5:39 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote: On 12/18/19 3:21 PM, Alberto Viana wrote: Hi Guys, I compiled my 389 with selinux enabled (--with-selinux): configure:21564: checking for --with-

[389-users] Re: selinux doubts

On 12/18/19 3:21 PM, Alberto Viana wrote: Hi Guys, I compiled my 389 with selinux enabled (--with-selinux): configure:21564: checking for --with-selinux configure:21575: result: yes with_selinux='yes' but If I ran dscreate interactive, shows me: selinux is disabled, will not relabel ports

[389-users] Re: dsconf problems

On 12/16/19 10:13 AM, Alberto Viana wrote: Hi Guys, I'm trying to config and enable uniqueness attribute plugin: ~# dsconf RNP plugin attr-uniq add "uid-test" --attr-name uid Successfully created the cn=uid-test,cn=plugins,cn=config if I try to enable it: ~# dsconf RNP plugin attr-uniq

[389-users] Re: cockpit plugin doubts

On 12/15/19 8:06 PM, Mark Reynolds wrote: On 12/13/19 8:29 PM, William Brown wrote: On 14 Dec 2019, at 11:07, Alberto Viana wrote: Hi Guys, In the old 389-console was possible to manage remote instances (installations in different machines) and what about in new UI?  Should I install

[389-users] Re: cockpit plugin doubts

On 12/13/19 8:29 PM, William Brown wrote: On 14 Dec 2019, at 11:07, Alberto Viana wrote: Hi Guys, In the old 389-console was possible to manage remote instances (installations in different machines) and what about in new UI? Should I install a cockpit plugin to each 389 machine in my

[389-users] Re: cockpit handlebars warning (npm)

On 12/13/19 8:42 AM, Alberto Viana wrote: Hi, During my tests and install of 389-ds cockpit plugin via npm I got this warning: "overview": "Versions of `handlebars` prior to 4.5.3 are vulnerable to prototype pollution. It is possible to add or modify properties to the Object prototype

[389-users] Re: cockpit problems

de trick, but it only works with root, if i try a user in the wheel/sudo group, shows me that message: ~# id myuser uid=1002(myuser) gid=1002(myuser) groups=1002(myuser),10(wheel) Does not suppose to work? Thanks. On Thu, Dec 12, 2019 at 1:43 PM Mark Reynolds mail

[389-users] Re: cockpit problems

that says: Reuse my password for privileged tasks  ? Thanks. On Thu, Dec 12, 2019 at 1:43 PM Mark Reynolds <mailto:mreyno...@redhat.com>> wrote: On 12/12/19 11:34 AM, Alberto Viana wrote: Viktor, Sorry, forgot to mention that. It was created using dscreate wit

[389-users] Re: cockpit problems

On 12/12/19 11:34 AM, Alberto Viana wrote: Viktor, Sorry, forgot to mention that. It was created using dscreate with a template file: dscreate from-file rnp-template and the log shows me that LDAPI is enabled: [12/Dec/2019:15:39:31.407250429 +] - INFO - slapd_daemon - Listening on

[389-users] Re: replication during indexing

On 12/9/19 4:13 PM, Crocker, Deborah wrote: I have a couple of consumers where I need to index a new attribute. Should I stop replication to them while this is taking place? Note that the index attribute will not be something that is replicated during this time. Running an indexing task

[389-users] Announcing 389 Directory Server 1.4.2.5

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

[389-users] Announcing 389 Directory Server 1.4.1.12

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

[389-users] Announcing 389 Directory Server 1.4.1.11

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

[389-users] Re: userPassword changed to PBKDF2_SHA256 after bind

On 11/29/19 10:27 AM, Francesc Guasch wrote: Hello. After upgrade to 389 release 1.4 I experienced an odd behaviour. If I add a new user, then I bind with that user. The userPassword attribute gets changed to {PBKDF2_SHA256}. These are the steps I follow to reproduce it: 1- add a new entry

[389-users] Re: Query about entryCSN and nsUniqueID in place of entryUUID

In my OpenLdap we have ACL policies is there any script available to convert OpenLDAP acl policies to 389-ds policies.? There is no script that I am aware of for such things.  You will need to recreate them manually. As for your IRC question, you can not have a single ACI with allow and

[389-users] Announcing 389 Directory Server 1.4.2.4

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

[389-users] Announcing 389 Directory Server 1.4.0.31

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

[389-users] Announcing 389 Directory Server 1.4.1.10

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

[389-users] Re: ERR - slapi_ldap_bind - Could not send bind request for id [(anon)] authentication mechanism [EXTERNAL]: error -1 (Can't contact LDAP server), system error 0 (no error), network error

On 11/12/19 4:47 PM, Graham Leggett wrote: Hi all, We have a long standing 389ds master LDAP server that was found to be unable to contact it’s slaves. Most specifically, the slaves show nothing in their logs about any kind of connection, while the master is logging this:

[389-users] Re: Using sec-activate to enable SSL for admin server

On 11/6/19 12:42 AM, Grant Byers wrote: Hi, I’ve mostly completed automated deployment of a 389ds cluster via Ansible. The final piece of the puzzle is the enablement of SSL/TLS for the Admin server.  From what I understand, I should be able to use the sec-activate tool to do this;

[389-users] Re: MMR Incremental Update running long with many changes sent

On 11/5/19 6:29 PM, Oleg Cohen wrote: Greetings, I am running 389-DS cluster v1.4.0.13 on CentOS 7. I have two nodes at the moment with a replication agreement set on both. I have initialized replica on NODE2 from NODE1. A replication agreement started from NODE2 to NODE1 and is now

[389-users] Announcing 389 Directory Server 1.4.0.30

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

[389-users] Announcing 389 Directory Server 1.4.2.3

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

[389-users] Announcing 389 Directory Server 1.4.1.9

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

[389-users] Re: Change User DS in Admin Server with command line

On 10/29/19 9:29 AM, Nicolas Martin wrote: Hello everyone, Since disabling the non secure port 389, I need to change the "User DS" setting of the admin server. I can do it fine with the GUI in the tab "User DS" and set my User Directory settings. However, I can't find which configuration

[389-users] Re: master to master replication cfg Q

On 10/22/19 12:38 PM, Simon Pichugin wrote: On Tue, Oct 22, 2019 at 03:58:40PM +, Ghiurea, Isabella wrote: Hi List, I have a question regarding the cfg for a slave replication ldap server: we have 2 DS cfg as master to master replication with only one acting as write

[389-users] Re: Binding when using database links

On 10/17/19 1:36 PM, Vandenburgh, Steve Y wrote: With database links - when connecting from one server to the linked-server, it is possible to rebind as the user instead of using specific proxy credentials? Sorry there is not. Thanks, Steve Vandenburgh This communication is the

[389-users] Re: Support for permissive modify

We do not currently support it, but we just opened a ticket a few days ago to add this feature: https://pagure.io/389-ds-base/issue/50645 Sorry no time line yet on when we are going to add it, but we are going to add it at some point. Mark On 10/15/19 2:52 PM, Keith Hazelton wrote: Does

[389-users] Re: 389 packages fail to upgrade on fedora 30

If this build works please give it karma: https://bodhi.fedoraproject.org/updates/FEDORA-2019-6214f75764 Thanks, Mark On 10/15/19 11:27 AM, Ldap Tester wrote: I don't know. It doesn't seem to be. There are no other packages obsoleting 389-admin. Adding --allowerasing to the dnf command does

[389-users] Re: 389 packages fail to upgrade on fedora 30

The admin and console packages are going away in F31 (fyi) So I'm seeing the same problem though, and it's probably the perl provide/requires filters we added to the spec file (ugh can't wait for 389-admin to go away).  Anyway, I'll need to do a new build on F30 to remove these perl

[389-users] Re: Support for permissivemodify change control

On 10/10/19 9:54 AM, Keith Hazelton wrote: Does 389 Directory Server support the permissive modify control? It allows modify operations to not error out when addiing an already present value to a multi-valued attribute and a delete value mod when the value is already gone. 389 DS does not

[389-users] Re: slapd start up problem

On 10/8/19 12:01 PM, Paul Whitney wrote: Hello, We have discovered that one of out test LDAPS servers has been down for sometime and we are not seeing anything that indicate why.  However, when we start the slapd-config instance up, it kicks off then dies with error "memory violation"

[389-users] Re: New Install - Port Question

On 10/4/19 9:43 AM, Townsley, Eric L wrote: Hi, I have just performed my first install of 389 Directory, no issues were encountered. Looks like I need our firewall opened for ports 389 and 9830 from my laptop for Directory Server and the Admin Server access sound correct? Correct, if you

[389-users] Re: adding users to LDAP

on managing and working with AD. Regards, Jonathan Aquilina Owner managing director Phone (356) 20330099 Mobile (356) 79957942 Email sa...@eagleeyet.net *From:* Mark Reynolds *Sent:* Thursday, October 3, 2019 2:07:27 PM

[389-users] Re: adding users to LDAP

On 10/3/19 6:04 AM, Jonathan Aquilina wrote: Are you aware if there are plans to extend cockpit functionality? Yes, the new Cockpit UI is in its infancy, and it currently only does Administration of the server, not the database content.  We are still working on getting all parts of the UI

[389-users] Announcing 389 Directory Server 1.4.1.8

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

[389-users] Announcing 389 Directory Server 1.4.2.2

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

[389-users] Re: Replication with SSLCLIENTAUTH: server sent no certificate

On 9/25/19 10:43 AM, Eugen Lamers wrote: I'm trying to setup a replication with a certificate based authentication between supplier and consumer. The certificates in the certdb at /etc/dirsrv/slapd-XXX contain the very same CA with which the respective server certificates in the certdbs have

[389-users] Re: sudoers tree missing on a 389-ds replica

On 9/23/19 11:15 AM, Sergei Gerasenko wrote: Hello, I’ve run into an interesting situatuion with the sudoers tree in 389-ds. All the nodes in the 389-ds cluster have it, but one doesn’t. I’ve tried dumping the database on a good node with db2ldif and reloading on the bad node with ldif2db,

[389-users] Re: 389ds ldaps issue after upgrade

On 9/17/19 10:48 AM, Mihai Carabas wrote: After investigating, it seems that no cypersuite is available in NSS3.44, from the ones I have: [17/Sep/2019:17:17:51.043017973 +0300] - WARN - Security Initialization - SSL alert: Cipher suite rsa_null_md5 is not available in NSS 3.44. Ignoring

[389-users] Re: 389ds ldaps issue after upgrade

On 9/17/19 10:42 AM, William Brown wrote: Hey there, Can you send us the access log of the connection attempt, as well as the command line options you used to make the connection? What was the previous version of DS you were using? Thanks! On 17 Sep 2019, at 16:40, Mihai Carabas

[389-users] Re: FIPS 140-2 and dirsrv-admin

Server build I made for you that might fix all the FIPS issues? Mark Paul M. Whitney On 9/5/19, 9:17 AM, "Mark Reynolds" wrote: On 8/30/19 9:12 PM, William Brown wrote: > >> On 31 Aug 2019, at 03:07, Mark Reynolds wrote: >> >>

[389-users] Re: FIPS 140-2 and dirsrv-admin

: On 31 Aug 2019, at 03:07, Mark Reynolds wrote: Well... not to be a messenger of bad news, but 389-admin/389-console & friends are deprecated. We are not doing any more bug fixes around these packages. The old java console has been replaced by a Cockpit plugin in Fedora31/RHEL8/CentOS8.

[389-users] Re: sync AD account state

On 9/5/19 5:16 AM, DaV wrote: Hi guys, How can I sync account state from Windows AD to 389ds 1. account disabled 2. account lockout 3. password expired I want to sync these attributes from Windows AD to 389ds, would you please tell me? Thanks in advance. Well according to the docs password

[389-users] Re: FIPS 140-2 and dirsrv-admin

On 8/30/19 9:12 PM, William Brown wrote: On 31 Aug 2019, at 03:07, Mark Reynolds wrote: Well... not to be a messenger of bad news, but 389-admin/389-console & friends are deprecated. We are not doing any more bug fixes around these packages. The old java console has been repl

[389-users] Reminder of 389-admin, console, and webapp deprecation & removal

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

[389-users] Re: Adding fields for "NT" and "Posix" User to the web gui gateway interface

On 8/30/19 1:02 PM, Janet Houser wrote: Hi Folks, I've just started to play with the "Directory Server Gateway" options to add users and groups.  One think I've noticed is that the default user form doesn't have a way to enable "NT User" or "Posix User" attributes or the ability to add info

[389-users] Re: FIPS 140-2 and dirsrv-admin

Well... not to be a messenger of bad news, but 389-admin/389-console & friends are deprecated.  We are not doing any more bug fixes around these packages.  The old java console has been replaced by a Cockpit plugin in Fedora31/RHEL8/CentOS8. Sorry, Mark On 8/30/19 11:37 AM, Paul Whitney

[389-users] Re: LDAp password error

On 8/26/19 4:33 PM, Fernando Fuentes wrote: Hello All, I am using a web ui to add end delete users. When I reset or try to add a password I get: LDAP error, server says: Constraint violation - invalid password syntax - passwords with storage scheme are not allowed What do I need to turn on

[389-users] Re: Test LDAP client connection

On 8/26/19 2:50 PM, Nicolas Kovacs wrote: Hi, So it looks like my 389 DS server is running. I admit I'm fighting every step to get this thing to run. As it looks, the next step is to test the LDAP client connection. Which leads me to my first question. When TLS is enabled, is it still

[389-users] Re: Windows Sync Agreement issue

On 8/23/19 5:38 AM, DaV wrote: Hi all, For OneWaySync, AD to 389ds. I have read this guide https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/using_windows_sync-modifying_the_sync_agreement Synchronization works two ways. The Directory Server

[389-users] Re: 389 Directory Install Question

On 8/7/19 11:00 AM, Townsley, Eric L wrote: Hi, Do you have to install as root? Yes, unless you are building the server yourself from source code, and do a "prefix" build (which installs the package into a custom location) Thanks Eric

[389-users] Announcing 389 DIrectory Server 1.4.0.27

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

<    1   2   3   4   5   6   7   8   9   >