Ticket was cloned from Red Hat Bugzilla (product Red Hat Directory Server): Bug 1091633
Encryption tab not working any more on ds console windows, C:\Program Files\389 Management Console>"java" "-Djava.library.path=." -cp "./js s4.jar;./ldapjdk.jar;./idm-console-base.jar;./idm-console-mcc.jar;./idm-c onsole-mcc_en.jar;./idm-console-nmclf.jar;./idm-console-nmclf_en.jar;./389-cons ole_en.jar" -Djava.util.prefs.systemRoot=/.389-console -Djava.util.prefs.userRoot=/.389-console com.netscape.management.client.console.Console 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$CreateT abAction.run(Unknown Source) at com.netscape.management.admserv.config.BaseConfigPanel$4.run(UnknownSource)
NOTE: This may be a windows only problem, and it may be a problem with the version of Java being used on Windows.
This may be a Windows only issue. What version of Windows are you using? What version of the Windows Console package are you using? What version of Java are you using?
Info from reporter:
Windows XP and Windows 7 both 64 bit. Java installed 64 bit and version 7 update 55.
Console is 389-Console-1.1.6-x86_64.msi
I could reproduce the problem on Windows 389-console 1.1.6, but not on 1.1.7, on which there is no problem to choose the encryption tab.
Note: even on 1.1.6, the problem occurs on the Admin Console only. No problem on the Directory Console.
Rebuild Console for Windows should fix this issue.
Metadata Update from @nhosoi: - Issue assigned to nhosoi - 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/1120
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: Fixed)