Admin server can be configured to use SSL and so when console connects to admin server, it prompts user to verify certificate supplied by Admin server. That will issue security warning:
"The certificate this server present is either untrusted or unknown.
This server can only communicate through a secure connection involving a certificate.
Do you wish to accept this certificate anyway ?
\Checkbox Accept this certificate for this session only."
Checkbox is unchecked by default, so certificate should be accepted for all subsequent sessions. This is NOT true and such certificate caching is not working. Currently, checkbox is useless.
Steps to Reproduce: Setup: enable SSL for admin server, connect to https://localhost:9830
1) certutil -d ~/.redhat-idm-console -L
// no certificate
2) When I am asked about new certificate, I check Accept this certificate for this session only.
3) certutil -d ~/.redhat-idm-console -L
// still no certificate
4) Re-login, when I am asked about new certificate, I uncheck Accept this certificate for this session only, this is where I expect certificate to be cached
5) certutil -d ~/.redhat-idm-console -L
Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI
CN=admin P,,
// certificate cached succesfully
6) Re-login, now I do NOT expect question about new/untrusted certificate. Certificate is known (i.e. present in certdb of console) and trusted ("P,,"), but abovementioned security warning still pops up.
Actual results: Certificate caching doesn`t work
Expected results: Certificate caching should make security warning go away.
This works for me using the latest version.
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/807
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)