Problem browsing LDAP with Outlook
by Chris Bryant
When configuring Microsoft Outlook (not Outlook Express) to access an LDAP directory, there is an option to 'Enable Browsing (requires server support)'. If this option is chosen and the directory server supports it, then you should be able to open the LDAP address book and page up and down through the results. I have been unable to get this working properly with 389 DS.
When I try to browse from Outlook against the 389 DS directory, I am able to see the first page of results perfectly. However, if I move to the next page, only the first object returned will have any attributes included, and all of the rest of the objects in the page will have no attributes. I have a test perl script that duplicates this functionality as well.
I can get this to work properly with an older version of Netscape Directory Server, and I can get it working with OpenDS. Since 389 DS advertises support for the controls that are required for this to work, just like the other two servers, then I would expect it to work there also.
Has anyone out there gotten this to work with 389 DS? If so, can you share if there was anything special that you needed to do to get this to work? I'm trying to determine if this is a bug in the server, or if I'm just missing something in the configuration.
Thanks,
Chris
USA.NET
You Run Your Business. We'll Run Your Email.
This message is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information of USA.NET, Inc. Any unauthorized review, use, copying, disclosure, or distribution is prohibited. If you are not the intended recipient, please immediately contact the sender by reply email and delete all copies of the original message.
3 years, 8 months
Re: [389-users] get base dn from ldapsearch
by Angel Bosch Mora
> Maybe I am understanding this wrong but could you not just check in
> the config what the search base is set to on the client side? What is
> the problem you are trying to solve?
>
yes, you're right. i can just take a look at ldap.conf but there's several places to look:
- debian/ubuntu uses /etc/ldap/ldap.conf
- RHEL/CentOS uses /etc/openldap/ldap.conf
- custom compilations can use any path. ex: /usr/local/ldap/ldap.conf
- windows openldap uses... i don't really know :P
so what im trying to do is resolving configured base without knowing anything about the client.
for example, this command gives me the server even if i dont know anything about the conf:
ldapsearch -d1 -x -LLL "(uid=example)" uid 2>&1 | grep ldap_connect_to_host
im just a little bit surprised that i can't find any debuglevel that gives me the BASE
abosch
12 years, 9 months
ldapsearch to get users with expired password
by Juan Asensio Sánchez
Hi
Is there any way to obtain the users with expired/expiring password?
Hi have activated the password policy, making the password expire
after X days, and warn them after X-10 days. Now, I want to create a
cron job to send an email to users warning them about its password
expiration. I know I can get that information about the user is
binding, but not for the users obtained from a search.
Thanks in advance.
13 years, 1 month
Manage Certificates button item (slightly different)
by Christopher Wood
These bugs are almost exactly the issue I'm experiencing:
https://bugzilla.redhat.com/show_bug.cgi?id=430499
https://bugzilla.redhat.com/show_bug.cgi?id=442103
In my case, the admin server on host1 can use the "Manage Certificates" button on the admin server, and the directory server installed on the same host. So the bug is not happening to me.
However, I get "java.net.ConnectException: Connection refused" when I use the "Manage Certificates" button on host2's directory server that I registered with host1's admin server.
I don't get any output on the console when I repeat this procedure having run 389-console from the command line. I don't see anything immediately obvious under /var/log/dirsrv/*/errors on both servers. I can run ldapsearch against ldaps://host1 and ldaps://host2.
Would you list denizens possibly have any hints as to how to troubleshoot this?
13 years, 1 month
NPE in manage certificates
by Adrian Bridgett
Just in case anyone else is bitten by this which seems to have several
causes, here's another one. Thought it worth posting in case it saves
someone else some headscratching time!
Don't install centos-ds-admin and let it pull adminutil from EPEL
(rather than adminutil from centosextras). If you do, then clicking
"manage certificates" on the LDAP server (not the admin server) yields:
(389-ds-admin-console from ubuntu which is sadly 1.1.3, but I also
tried the windows binary which also errored the same way)
~$ Exception in thread "AWT-EventQueue-0"
java.lang.NullPointerException
at
com.netscape.management.client.security.CertificateDialog.<init>(Unknown
Source)
at
com.netscape.management.client.security.CertificateDialog.<init>(Unknown
Source)
at com.netscape.admin.dirserv.task.KeyCert.run(Unknown Source)
at com.netscape.management.client.TaskModel.actionObjectRun(Unknown
Source)
at
com.netscape.management.client.TaskPage$TaskList$ButtonMouseListener.mouseClicked(Unknown
Source)
at
java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:270)
at java.awt.Component.processMouseEvent(Component.java:6111)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:5873)
at java.awt.Container.processEvent(Container.java:2105)
at java.awt.Component.dispatchEventImpl(Component.java:4469)
at java.awt.Container.dispatchEventImpl(Container.java:2163)
at java.awt.Component.dispatchEvent(Component.java:4295)
at
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4461)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4134)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4055)
at java.awt.Container.dispatchEventImpl(Container.java:2149)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4295)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:604)
at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
Currently waiting on our provider to sort their systems out so we can
use RHDS.
Adrian
--
bitcube.co.uk - Expert Linux infrastructure consultancy
Puppet, Debian, Red Hat, Ubuntu, CentOS
13 years, 1 month
Announcing 389 Directory Server version 1.2.8 Alpha 3
by Rich Megginson
The 389 Project team is pleased to announce the release of
389-ds-base-1.2.8 Alpha 3. This release has fixes for bugs found in
1.2.8 alpha testing and bugs from earlier releases.
Installation
yum install --enablerepo=updates-testing 389-ds
# or for EPEL
yum install --enablerepo=epel-testing 389-ds
setup-ds-admin.pl
Upgrade
yum upgrade --enablerepo=updates-testing 389-ds-base
idm-console-framework 389-admin 389-ds-console 389-admin-console
# or for EPEL
yum upgrade --enablerepo=epel-testing 389-ds-base
idm-console-framework 389-admin 389-ds-console 389-admin-console
setup-ds-admin.pl -u
How to Give Feedback
The best way to provide feedback is via the Fedora Update system. Each
update is broken down by package and platform. For example, if you are
using Fedora 13, and you have successfully installed or upgraded all of
the packages, and the console and etc. works, then go to the links below
for Fedora 13 and provide feedback.
* 389-ds-base-1.2.8.a3
** EL-5 -
https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.3.a3.el5
** Fedora 13 -
https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.3.a3.fc13
** Fedora 14 -
https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.3.a3.fc14
** Fedora 15 -
https://admin.fedoraproject.org/updates/389-ds-base-1.2.8-0.3.a3.fc15
scroll down to the bottom of the page, and click on the Add a comment >>
link
* select one of the Works for me or Does not work radio buttons, add
text, and click on the Add Comment button
If you are using a build on another platform, just send us an email to
389-users(a)lists.fedoraproject.org
Reporting Bugs
If you find a bug, or would like to see a new feature, you can enter it
here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
More Information
* Release Notes - http://port389.org/wiki/Release_Notes
* Install_Guide - http://port389.org/wiki/Install_Guide
* Download - http://port389.org/wiki/Download
13 years, 2 months
Sub suffixes, databases and permissions problem
by Diego Woitasen
Hi,
I have several sub suffixes with their databases. Sub-Suffix and database
creation works fine from the 389-console. When I try to create the OU that
matchs with the suffix I get error 50 (Insufficient permission of something
like that, I don't remember right now). I log to the console using the admin
user. That user has full permission on the whole tree. I can create the OU
if the sub-suffix and the database doesn't exists. The only way that I found
to create the OU is using the "directory manager", using ldapadd from
command line. After that, I can create anything in the subtree with the
admin user.
I also tried with another user that has full permission on the tree from
command line and fails with error 50 too.
It looks like permissions inheritance doesn't apply in the object that
matchs with the sub-suffix.
Regards,
Diego
--
Diego Woitasen
13 years, 2 months
389 not staying available.
by Gordon Cooke
I ran a yum update on one of my 2 LDAP server last night and am encountering this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=668619
yum installed as follows:
[root@blair slapd-blair]# rpm -qa |grep 389
389-adminutil-1.1.13-1.el5
389-ds-console-1.2.3-1.el5
389-dsgw-1.1.6-1.el5
389-admin-console-doc-1.1.5-1.el5
389-admin-1.1.14-1.el5
389-admin-console-1.1.5-1.el5
389-console-1.1.4-1.el5
389-ds-base-1.2.7.5-1.el5
389-ds-console-doc-1.2.3-1.el5
389-ds-1.2.1-1.el5
I am wondering if there is a known workaround for this short of recompiling with the changes identified in the patch. This is on RHEL5.6
Thanks for your help!!
Gordon
13 years, 2 months
Databases and sub suffixes from the command line
by Diego Woitasen
Hi,
I need to create 150 sub suffixes with their databases using the command
line (I need subtree replication to 150 branches). I read the RHDS
documentation and created the following entries:
ldapadd -x -D uid=scriptuser,ou=People,dc=domain,dc=ar -w foo << EOF
dn: cn=ou=$1\,dc=domain\,dc=ar,cn=mapping tree,cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsMappingTree
nsslapd-state: backend
nsslapd-backend: $1
nsslapd-parent-suffix: dc=domain,dc=ar
cn: ou=$1\,dc=domain\,dc=ar
dn: cn=$1,cn=ldbm database,cn=plugins,cn=config
objectclass: extensibleObject
objectclass: nsBackendInstance
nsslapd-suffix: ou=$1,dc=domain,dc=ar
dn: ou=$1,dc=domain,dc=ar
objectClass: organizationalUnit
objectClass: top
ou: $1
description: $1
EOF
The bind user has permission to add these entries to cn=config. Their are
created without error. The problem is the database. It looks like something
is missing in the filesystem:
#ls -l /var/lib/dirsrv/slapd-mreldc03/db/test
total 20
-rw------- 1 ldap ldap 46 Feb 23 20:41 DBVERSION
-rw------- 1 ldap ldap 16384 Feb 23 20:41 id2entry.db4
If I add an object to the suffix, nothing changes in the DB directory.
Using the Java Console, works perfectly. There are a lot of files in the DB
directory and that files are updates if a change something in the subtree.
May be I'm missing a step, but I reviewed the documention and my procedure
looks fine.
Regards,
Diego
--
Diego Woitasen
13 years, 2 months
issues with 1.2.7.5
by Robert Viduya
I'm having problems trying to get a clean install of 1.2.7.5 working. We're running RHEL5 and I have the EPEL5.4 repositories configured on it. Yum installed the following when I installed 389-ds:
389-admin.x86_64 1.1.13-1.el5 installed
389-admin-console.noarch 1.1.5-1.el5 installed
389-admin-console-doc.noarch 1.1.5-1.el5 installed
389-adminutil.x86_64 1.1.8-4.el5 installed
389-console.noarch 1.1.4-1.el5 installed
389-ds.noarch 1.2.1-1.el5 installed
389-ds-base.x86_64 1.2.7.5-1.el5 installed
389-ds-base-devel.x86_64 1.2.7.5-1.el5 installed
389-ds-console.noarch 1.2.3-1.el5 installed
389-ds-console-doc.noarch 1.2.3-1.el5 installed
389-dsgw.x86_64 1.1.5-1.el5 installed
idm-console-framework.noarch 1.1.5-4.el5 installed
After installation, I ran /usr/sbin/setup-ds-admin.pl to set up the initial configuration. Immediately after that, if I run 389-console, login as "cn=Directory Manager", navigate to "Directory Server" window and then try to open the "Configuration" tab, I get a dialog box that says: "Insufficient Permissions / The user cn=Directory Manager does not have permission to perform this operation.". Clicking the OK button gets me a new login window, but re-entering the Directory Manager credentials doesn't do anything. All I get is a blank page instead of what's supposed to be under the Configuration tab.
I've done the install a few times already to make sure I wasn't messing things up. There's nothing out of the ordinary in either the admin server error log or the directory server error log. The directory server access log shows only a few err=32, all under "ou=Global Preferences", which is probably expected on a completely new install.
The terminal window I ran 389-console shows a java stack trace, but only after I click past the error dialog box:
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at com.netscape.admin.dirserv.panel.ServerSettingsPanel$ReferralText.show(Unknown Source)
at com.netscape.admin.dirserv.panel.DSEntrySet.getAttributes(Unknown Source)
at com.netscape.admin.dirserv.panel.DSEntrySet.show(Unknown Source)
at com.netscape.admin.dirserv.panel.BlankPanel.refresh(Unknown Source)
at com.netscape.admin.dirserv.panel.BlankPanel.select(Unknown Source)
at com.netscape.admin.dirserv.panel.ContainerPanel.stateChanged(Unknown Source)
at javax.swing.JTabbedPane.fireStateChanged(JTabbedPane.java:417)
at javax.swing.JTabbedPane$ModelListener.stateChanged(JTabbedPane.java:270)
at javax.swing.DefaultSingleSelectionModel.fireStateChanged(DefaultSingleSelectionModel.java:133)
at javax.swing.DefaultSingleSelectionModel.setSelectedIndex(DefaultSingleSelectionModel.java:67)
at javax.swing.JTabbedPane.setSelectedIndexImpl(JTabbedPane.java:616)
at javax.swing.JTabbedPane.setSelectedIndex(JTabbedPane.java:591)
at javax.swing.JTabbedPane.insertTab(JTabbedPane.java:730)
at javax.swing.JTabbedPane.addTab(JTabbedPane.java:797)
at com.netscape.admin.dirserv.panel.DSTabbedPanel.addTab(Unknown Source)
at com.netscape.admin.dirserv.panel.RootPanel.<init>(Unknown Source)
at com.netscape.admin.dirserv.node.RootResourceObject.getCustomPanel(Unknown Source)
at com.netscape.management.client.ResourceModel.getCustomPanel(Unknown Source)
at com.netscape.management.client.ResourcePage.valueChanged(Unknown Source)
at javax.swing.JTree.fireValueChanged(JTree.java:2826)
at javax.swing.JTree$TreeSelectionRedirector.valueChanged(JTree.java:3197)
at javax.swing.tree.DefaultTreeSelectionModel.fireValueChanged(DefaultTreeSelectionModel.java:646)
at javax.swing.tree.DefaultTreeSelectionModel.notifyPathChange(DefaultTreeSelectionModel.java:1095)
at javax.swing.tree.DefaultTreeSelectionModel.setSelectionPaths(DefaultTreeSelectionModel.java:304)
at javax.swing.JTree.setSelectionPaths(JTree.java:1616)
at javax.swing.JTree.setSelectionRows(JTree.java:1689)
at javax.swing.JTree.setSelectionRow(JTree.java:1664)
at com.netscape.management.client.ResourcePage.pageSelected(Unknown Source)
at com.netscape.admin.dirserv.DSResourcePage.pageSelected(Unknown Source)
at com.netscape.management.client.Framework$TabChangeListener.stateChanged(Unknown Source)
at javax.swing.JTabbedPane.fireStateChanged(JTabbedPane.java:417)
at javax.swing.JTabbedPane$ModelListener.stateChanged(JTabbedPane.java:270)
at javax.swing.DefaultSingleSelectionModel.fireStateChanged(DefaultSingleSelectionModel.java:133)
at javax.swing.DefaultSingleSelectionModel.setSelectedIndex(DefaultSingleSelectionModel.java:67)
at javax.swing.JTabbedPane.setSelectedIndexImpl(JTabbedPane.java:616)
at javax.swing.JTabbedPane.setSelectedIndex(JTabbedPane.java:591)
at javax.swing.plaf.basic.BasicTabbedPaneUI$Handler.mousePressed(BasicTabbedPaneUI.java:3631)
at java.awt.Component.processMouseEvent(Component.java:6105)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:5873)
at java.awt.Container.processEvent(Container.java:2105)
at java.awt.Component.dispatchEventImpl(Component.java:4469)
at java.awt.Container.dispatchEventImpl(Container.java:2163)
at java.awt.Component.dispatchEvent(Component.java:4295)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4461)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4122)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4055)
at java.awt.Container.dispatchEventImpl(Container.java:2149)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4295)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:604)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
13 years, 2 months
