Opening the Encryption tab in Administration Server causes the follwoing exception to be thrown in the 389-Console client on M$ Windows 7, possible cause Java 1.7 (see mailing list thread):
Exception in thread "LongAction" java.lang.NoSuchMethodError: com.netscape.management.client.security.CipherPreferenceDialog.<init>(Ljava/awt/Frame;ZZZZZZ)V at com.netscape.management.admserv.panel.TurnOnSSL.setSecurityIsDomestic(Unknown Source) at com.netscape.management.client.security.EncryptionPanel.<init>(Unknown Source) at com.netscape.management.client.security.EncryptionPanel.<init>(Unknown Source) at com.netscape.management.admserv.panel.TurnOnSSL.getPanel(Unknown Source) at com.netscape.management.admserv.config.TabbedConfigPanel$CreateTabAction.run(Unknown Source) at com.netscape.management.admserv.config.BaseConfigPanel$4.run(Unknown Source) ResourceSet: found in cache loader558648009:com.netscape.management.client.util.default ResourceSet: found in cache loader558648009:com.netscape.management.client.util.default ResourceSet: found in cache loader558648009:com.netscape.management.client.util.default
Client Host OS:
Windows 7 Professional Service Pack 1 x86)64
Java Version:
java version "1.7.0_01" Java(TM) SE Runtime Environment (build 1.7.0_01-b08) Java HotSpot(TM) 64-Bit Server VM (build 21.1-b02, mixed mode)
Console Client:
389-Console-1.1.6-x86_64.msi
Mailing list thread: http://lists.fedoraproject.org/pipermail/389-users/2012-February/014075.html
Same problem encounted with Java 1.6
{{{ java version "1.6.0_29" Java(TM) SE Runtime Environment (build 1.6.0_29-b11) Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode) }}}
This problem doesn't exist in the CentOS distribution of Directory Server 8.1 on RHEL 5.6 {{{ $ rpm -qa | grep centos-ds centos-ds-base-8.1.0-0.14.el5.centos.2 centos-ds-console-8.1.0-5.el5.centos.2 centos-ds-admin-8.1.0-9.el5.centos.1 centos-ds-8.1.0-1.el5.centos.2 }}}
set default ticket origin to Community
Added initial screened field value.
I installed Sun/Oracle Java 1.7.0_67-b01 on Windows Server 2012R2. 389-Console 1.1.6 starts and works without any problem.
Metadata Update from @brett: - Issue set to the milestone: 389-admin,console 1.1.36
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/288
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)