SSCA usage is discouraged for production usage. Therefore, this should be warned about during health checking.
Some checks could be: - Checking for the presence of /etc/dirsrv/ssca (minor issue, but an issue since this makes people more prone to actually use it). - Check each instance's cert for being signed by SSCA. - Check if we trust the SSCA.
Credits: William (source)
1.4.2+
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.2
Metadata Update from @mreynolds: - Issue priority set to: normal - Issue tagged with: Healthcheck
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.3 (was: 1.4.2)
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/3814
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.