[389-users] Announcing 389 Directory Server 1.4.1.1

[Mark Reynolds]

   389 Directory Server 1.4.1.1

The 389 Directory Server team is proud to announce 389-ds-base version 
1.4.1.1


Fedora packages are available on Fedora 30 (rawhide).

https://koji.fedoraproject.org/koji/taskinfo?taskID=32348343 
 - Fedora 
30 (rawhide)


The new packages and versions are:

 * 389-ds-base-1.4.1.1-1

Source tarballs are available for download at Download 
389-ds-base Source 




 Highlights in 1.4.1.1

 * Version change


 Installation and Upgrade

See Download  for 
information about setting up your yum repositories.


To install, use *dnf install 389-ds-base cockpit-389-ds* After install 
completes, run *dscreate interactive*


There are no upgrade steps besides installing the new rpms

See Install_Guide 
 for 
more information about the initial installation and setup


See Source  
for information about source tarballs and SCM (git) access.



 Feedback

We are very interested in your feedback!

Please provide feedback and comments to the 389-users mailing list: 
https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.org


If you find a bug, or would like to see a new feature, file it in our 
Pagure project: https://pagure.io/389-ds-base


 * Bump version to 1.4.1.1
 * Ticket 50151 - lib389 support cli add/replace/delete on objects
 * Ticket 50041 - CLI and WebUI - Add memberOf plugin functionality
 * Rebased from 389-ds-base-1.4.0.20-1

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Re: Import an ldif

[Mark Reynolds]

On 1/30/19 3:58 PM, john.ber...@us.fujitsu.com wrote:


We are trying to import an ldif file from our old Sun One Directory 
Server 5.2. We have the 389 server set up and running. I can 
initialize the database I want to import in and it seems to work fine. 
However, we have a lot of users that do not get imported in due a 
syntax error on certain attributes because they are blank. Example:  
We have an attribute called Title which was never required so many of 
the users have it blank. These error on import. *Is there a way to get 
the 389 server to disregard that and load the user anyway? Basically 
we want to pull everything in even if the fields are blank.*


Ideally you could write a script to strip those empty attributes from 
the LDIF.


Otherwise you can turn off schema checking (syntax checking might also 
need to be disabled)


cn=config
nsslapd-schemacheck: off
nsslapd-syntaxcheck: off

Use ldapmodify to set these attributes (same as Sun DS), and stop the 
server before you import.  After the import completes you should turn 
these settings back "on".


HTH,

Mark

*
*

*
*


**

Regards,

John


___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Import an ldif

[john.ber...@us.fujitsu.com]

We are trying to import an ldif file from our old Sun One Directory Server 5.2. 
We have the 389 server set up and running. I can initialize the database I want 
to import in and it seems to work fine. However, we have a lot of users that do 
not get imported in due a syntax error on certain attributes because they are 
blank. Example:  We have an attribute called Title which was never required so 
many of the users have it blank. These error on import.  Is there a way to get 
the 389 server to disregard that and load the user anyway? Basically we want to 
pull everything in even if the fields are blank.

Regards,

John
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org