https://bugzilla.redhat.com/show_bug.cgi?id=627780
Description of problem: When tunring on SSL in either the dirsrv or the admin console, the next console start has this really oversized popup window to just accept a new untrusted certificate, although the CA cert was edited with correct trusted flags. server-cert u,u,u Certificate Authority CT,, Seen this before and this is not easy to verify/read what it wants when using twm, for example. Version-Release number of selected component (if applicable): idm-console-framework-1.1.5-1.el5idm redhat-admin-console-8.2.0-2.el5dsrv redhat-ds-console-8.2.0-4.el5dsrv redhat-idm-console-1.0.2-1.el5idm How reproducible: always, have seen this for a while, probably 8.0, 8.1 Steps to Reproduce: 1.configure dirsrv or admin for SSL 2.restart redhat-idm-console 3.try to open the console Actual results: have this very large popup window with title "Security Warning" to accept a new untrusted certificate Expected results: much smaller popup window that fit the screen. Additional info: I noticed the first time I opened the console using https, after the popup security warning, there was a connection error and then it connected just fine, no logs, not sure why it did this.
batch update moving tickets to future
set default ticket origin to Community
Added initial screened field value.
The popup window is appropriately sized. It really can not be made any smaller, and I do not get any connection errors. Closing as works for me.
Metadata Update from @mreynolds: - Issue assigned to mreynolds - 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/200
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)
Login to comment on this ticket.