On 02/24/2011 09:09 AM, Roy McMorran wrote:
Robert Viduya<robert+fds<at> shangri-la.ts.gatech.edu>
writes:
> 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
> 389-admin-console.noarch 1.1.5-1.el5
> 389-admin-console-doc.noarch 1.1.5-1.el5
> 389-adminutil.x86_64 1.1.8-4.el5
> 389-console.noarch 1.1.4-1.el5
> 389-ds.noarch 1.2.1-1.el5
> 389-ds-base.x86_64 1.2.7.5-1.el5
> 389-ds-base-devel.x86_64 1.2.7.5-1.el5
> 389-ds-console.noarch 1.2.3-1.el5
> 389-ds-console-doc.noarch 1.2.3-1.el5
> 389-dsgw.x86_64 1.1.5-1.el5
> idm-console-framework.noarch 1.1.5-4.el5
>
> 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.
>
<snip>
I'm curious if there has been any update on this issue. I'm seeing the exact
same behavior on a new install and it's preventing me from getting SSL
configured. I can't get to that configuration tab without getting the Java
NPE and the login prompt. Re-logging in doesn't help, and it matters not
whether I use directory manager or admin.
I'm on slightly newer versions:
389-ds-console-1.2.3-1.el5
389-ds-base-devel-1.2.8-0.2.a2.el5
389-ds-1.2.1-1.el5
389-adminutil-1.1.13-1.el5
389-admin-1.1.14-1.el5
389-admin-console-1.1.5-1.el5
389-dsgw-1.1.6-1.el5
389-admin-console-doc-1.1.5-1.el5
389-adminutil-devel-1.1.13-1.el5
389-console-1.1.4-1.el5
389-ds-base-1.2.8-0.2.a2.el5
Has anyone found a workaround?
If you are referring to
https://bugzilla.redhat.com/show_bug.cgi?id=661116
You get an error, but you should be able to just ignore the error and
proceed anyway.
There is a fix in updates testing which should be hitting the mirrors
today or tomorrow.
Thank you.
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users