Red Hat Bugzilla – Bug 528274
389 Console has been nonfunctional since rename
Last modified: 2011-04-25 19:28:06 EDT
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):
Steps to Reproduce:
1.Launch 389-console from terminal or "run-application"
2.Fill in username, password and url:port
4.The console now hangs at Authorizing... until the java process is killed.
Frozen app. Program is utterly unusable.
DS console working just as well as fedora-ds-console
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.
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 ***