Bug 528274 - 389 Console has been nonfunctional since rename
Summary: 389 Console has been nonfunctional since rename
Keywords:
Status: CLOSED DUPLICATE of bug 520493
Alias: None
Product: Fedora
Classification: Fedora
Component: 389-admin-console
Version: 11
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-10 15:29 UTC by Benjamin Kingston
Modified: 2011-04-25 23:28 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-10-12 15:20:01 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Benjamin Kingston 2009-10-10 15:29:52 UTC 
Description of problem:
When loggin into https/ldaps only admin server, 389 hands on:

Authorizing user "root"

Very annoying, and the previous version that was the Fedora Console works fine.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Launch 389-console from terminal or "run-application"
2.Fill in username, password and url:port
3.Click OK
4.The console now hangs at Authorizing... until the java process is killed.
  
Actual results:
Frozen app. Program is utterly unusable.

Expected results:
DS console working just as well as fedora-ds-console

Additional info:

Tested with Java 1.6u16 from java.com mostly, but some tests with OSS java 1.6.b16

x86_64, java.com is set as default jvm.
Comment 1 Rich Megginson 2009-10-12 15:20:01 UTC 
The upgrade from Fedora DS to 389 DS breaks your SSL/TLS console configuration.  This is related to https://bugzilla.redhat.com/show_bug.cgi?id=520493, https://bugzilla.redhat.com/show_bug.cgi?id=495073, and https://bugzilla.redhat.com/show_bug.cgi?id=501846.

These bugs have been fixed in 1.2.3.  If you are able, I suggest upgrading to the testing release of 1.2.3 and running setup-ds-admin.pl -u and see if that fixes your problems.

*** This bug has been marked as a duplicate of bug 520493 ***
Note You need to log in before you can comment on or make changes to this bug.