add user ldif via ldapadmin
by Todor Petkov
Hello,
we have just upgraded the DS server to Centos7, along with the versions
of 389* and ldapadmin:
389-console-1.1.18-1.el7.noarch
389-dsgw-1.1.11-5.el7.x86_64
389-ds-base-1.3.5.10-15.el7_3.x86_64
389-admin-console-1.1.12-1.el7.noarch
389-adminutil-1.1.21-2.el7.x86_64
389-admin-1.1.46-1.el7.x86_64
389-admin-console-doc-1.1.12-1.el7.noarch
phpldapadmin-1.2.3-5.el7.noarch
389-ds-console-doc-1.2.16-1.el7.noarch
389-ds-1.2.2-6.el7.noarch
389-ds-base-libs-1.3.5.10-15.el7_3.x86_64
389-ds-base-snmp-1.3.5.10-15.el7_3.x86_64
389-ds-console-1.2.16-1.el7.noarch
When I try to create new user via the "import" button in phpldapadmin,
it says:
LDAP said: Constraint violation
Error number: 0x13 (LDAP_CONSTRAINT_VIOLATION)
Description: Some constraint would be violated by performing the action.
This can happen when you try to add a second value to a single-valued
attribute, for example.
389-console is working fine.
I have exported the ldif for the newly created user, deleted it and
tried to import (in case I miss some entries), but it's the same.
Googling does not reveal any solution.
Anyone with similar experience and a fix?
Thanks in advance,
7 years, 2 months
Re: [389-devel] Re: Trac -> Pagure migration is complete
by Mark Reynolds
On 02/13/2017 05:51 AM, Simon Pichugin wrote:
> On Sat, Feb 11, 2017 at 05:23:24PM -0500, Mark Reynolds wrote:
>> Our migration to Pagure is complete. Please use this project for
>> filing Directory Server issues (aka Tickets):
>> [1]https://pagure.io/389-ds-base
>> Trac is now in read-only mode. If you need help with any of this just
>> send an email to [2]389-users(a)lists.fedoraproject.org or #389 channel
>> on IRC (freenode)
> Looks great! Thank you!
>
> What is about lib389 migration, btw?
> https://pagure.io/lib389
> Should we create new issues there?
Yes, but the source is not migrated yet. I'll be doing that today...
>
> Sorry if you've posted the info about lib389 migration already, I probably
> missed it.
>
>> On 02/08/2017 12:07 PM, Mark Reynolds wrote:
>>
>> We are planning on doing the Trac to Pagure migration this Friday.
>> Using Pagure is very similar to Trac, except you create "Issues"
>> instead of "tickets".
>> One change to keep in mind is that we now have separate projects for
>> our components like: admin server, 389-ds-console,
>> idm-console-framework, 389-dsgw, 389-ds-base, etc. These can all be
>> found under the Directory_Services group:
>> [3]https://pagure.io/group/Directory_Services
>> If you have an Admin Server issue to report create a new issue under
>> the 389-admin project, etc.
>> Please use the "389-ds-base" project for new Directory Server issues.
>> Note, your previous tickets you filed, or are following, will still
>> have the same ticket number:
>> [4]https://fedorahosted.org/389/ticket/48118
>> Will be:
>> [5]https://pagure.io/389-ds-base/issue/48118
>> Once the migration is complete there will be a final announcement, and
>> Trac will be put into read-only mode until it is decommissioned.
>> Regards,
>> Mark
>>
>> _______________________________________________
>> 389-announce mailing list -- [6]389-announce(a)lists.fedoraproject.org
>> To unsubscribe send an email to [7]389-announce-leave(a)lists.fedoraproject.org
>>
>> References
>>
>> 1. https://pagure.io/389-ds-base/issue/
>> 2. mailto:389-users@lists.fedoraproject.org
>> 3. https://pagure.io/group/Directory_Services
>> 4. https://fedorahosted.org/389/ticket/48118
>> 5. https://pagure.io/389-ds-base/issue/
>> 6. mailto:389-announce@lists.fedoraproject.org
>> 7. mailto:389-announce-leave@lists.fedoraproject.org
>> _______________________________________________
>> 389-devel mailing list -- 389-devel(a)lists.fedoraproject.org
>> To unsubscribe send an email to 389-devel-leave(a)lists.fedoraproject.org
>
>
> _______________________________________________
> 389-devel mailing list -- 389-devel(a)lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-leave(a)lists.fedoraproject.org
7 years, 2 months
Trac -> Pagure Migration this Friday (Feb 10)
by Mark Reynolds
We are planning on doing the Trac to Pagure migration this Friday.
Using Pagure is very similar to Trac, except you create "Issues" instead
of "tickets".
One change to keep in mind is that we now have separate projects for our
components like: admin server, 389-ds-console, idm-console-framework,
389-dsgw, 389-ds-base, etc. These can all be found under the
Directory_Services group:
https://pagure.io/group/Directory_Services
If you have an Admin Server issue to report create a new issue under the
389-admin project, etc.
Please use the "389-ds-base" project for new Directory Server issues.
Note, your previous tickets you filed, or are following, will still have
the same ticket number:
https://fedorahosted.org/389/ticket/48118
Will be:
https://pagure.io/389-ds-base/issue/48118
Once the migration is complete there will be a final announcement, and
Trac will be put into read-only mode until it is decommissioned.
Regards,
Mark
7 years, 2 months
Red Hat Directory Server 10 Import Fails
by Paul Whitney
I am testing Red Hat Directory Server 10. I tried importing userRoot database into RHDS 10. During import, the process (str2entry_dupcheck) complained of a duplicate value and then stopped the import process and cleared out the userRoot director in /var/lib/dirsrv/slapd-users/db.
Is there a workaround to get past this? Can I config the dse.ldif file to ignore this situation?
Hitting Google yielded a similar scenario...https://bugzilla.redhat.com/show_bug.cgi?id=918713
But that was closed several years ago.
Paul M. Whitney
E-mail: paul.whitney(a)mac.com
7 years, 2 months