Este conteúdo não está disponível no idioma selecionado.
Using IdM Healthcheck to monitor your IdM environment
Performing status and health checks
Abstract
ipa-healthcheck utility helps administrators to detect problems in a Red Hat Identity Management (IdM) environment. This includes status checks of IdM services, configuration file permissions, replication statuses, and issues with certificates.
Providing feedback on Red Hat documentation Copiar o linkLink copiado para a área de transferência!
We appreciate your feedback on our documentation. Let us know how we can improve it.
Submitting feedback through Jira (account required)
- Log in to the Jira website.
- Click Create in the top navigation bar.
- Enter a descriptive title in the Summary field.
- Enter your suggestion for improvement in the Description field. Include links to the relevant parts of the documentation.
- Click Create at the bottom of the dialogue.
Chapter 1. Installing and running the IdM Healthcheck tool Copiar o linkLink copiado para a área de transferência!
Learn more about the IdM Healthcheck tool and how to install and run it.
- The Healthcheck tool is only available on RHEL 8.1 or later.
1.1. Healthcheck in IdM Copiar o linkLink copiado para a área de transferência!
The Healthcheck command line tool in Identity Management (IdM) helps find issues that can impact the performance of your IdM environment. Using Healthcheck, you can identify an issue in advance so that you can correct it before it becomes critical.
You can use Healthcheck without obtaining a Kerberos ticket.
Modules are independent
Healthcheck consists of independent modules which check for:
- Replication issues
- Certificate validity
- Certificate authority infrastructure issues
- IdM and Active Directory trust issues
- Correct file permissions and ownership settings
Output formats and destination
You can set the following types of output for Healthcheck to generate by using the output-type option:
-
json: Machine-readable output in JSON format (default) -
human: Human-readable output
You can specify a file to store the output by using the --output-file option.
Results
Each Healthcheck module returns one of the following results:
- SUCCESS
- The system is configured as expected.
- WARNING
- It is advisable to monitor or evaluate the configuration.
- ERROR
- The system is not configured as expected.
- CRITICAL
- The configuration is not as expected, with a significant potential to impact the functioning of your IdM deployment.
1.2. Installing IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
Learn how you can install the IdM Healthcheck tool.
Prerequisites
-
You are logged in as
root.
Procedure
Install the
ipa-healthcheckpackage:yum install ipa-healthcheck
[root@server ~]# yum install ipa-healthcheckCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteOn RHEL 8.1 and 8.2 systems, use the yum install /usr/bin/ipa-healthcheck command instead.
Verification
Perform a basic Healthcheck test:
ipa-healthcheck
[root@server ~]# ipa-healthcheck []Copy to Clipboard Copied! Toggle word wrap Toggle overflow The empty square brackets
[]indicate a fully-functioning IdM installation.
1.3. Running IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
You can execute Healthcheck tests in one of the following ways:
- Manually
- Automatically by using log rotation.
This section describes how to execute the tests manually.
Prerequisites
- The Healthcheck tool is installed. See Installing IdM Healthcheck.
Procedure
[Optional] To display a list of all available Healthcheck tests, enter:
ipa-healthcheck --list-sources
[root@server ~]# ipa-healthcheck --list-sourcesCopy to Clipboard Copied! Toggle word wrap Toggle overflow To run the Healthcheck utility, enter:
ipa-healthcheck
[root@server ~]# ipa-healthcheckCopy to Clipboard Copied! Toggle word wrap Toggle overflow
1.4. Log rotation Copiar o linkLink copiado para a área de transferência!
Log rotation creates a new log file every day and the files are organized by date. The date is included in the filename.
Using log rotation, you can configure the maximum number of log files to be stored. If this number is exceeded, the newest file replaces the oldest one. For example, if the maximum rotation number is thirty, the thirty-first log file replaces the first, that is the oldest one.
Log rotation reduces voluminous log files and organizes them. This helps you analyze the logs.
1.5. Running IdM Healthcheck on a schedule Copiar o linkLink copiado para a área de transferência!
Follow this procedure to configure IdM Healthcheck to run on a schedule. This includes configuring the following utilities:
-
The
systemdtimer to run the Healthcheck tool periodically and generate the logs. -
The
crondservice to ensure log rotation.
The default log name is healthcheck.log and the rotated logs use the healthcheck.log-YYYYMMDD format.
The Healthcheck timer tool is not a real-time tool. It is only meant to be run a few times an hour. If you require real-time monitoring of, for example, services or disk space, use a different tool.
Prerequisites
-
You have
rootprivileges.
Procedure
Enable a
systemdtimer:systemctl enable ipa-healthcheck.timer
# systemctl enable ipa-healthcheck.timer Created symlink /etc/systemd/system/multi-user.target.wants/ipa-healthcheck.timer -> /usr/lib/systemd/system/ipa-healthcheck.timer.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Start the
systemdtimer:systemctl start ipa-healthcheck.timer
# systemctl start ipa-healthcheck.timerCopy to Clipboard Copied! Toggle word wrap Toggle overflow Open the
/etc/logrotate.d/ipahealthcheckfile to configure the number of logs you want to be saved:[...] rotate 30 }[...] rotate 30 }Copy to Clipboard Copied! Toggle word wrap Toggle overflow By default, logs are stored for 30 days before they are overwritten by newer logs.
In the same file, configure the path to the file storing the logs.
/var/log/ipa/healthcheck/healthcheck.log { [...]/var/log/ipa/healthcheck/healthcheck.log { [...]Copy to Clipboard Copied! Toggle word wrap Toggle overflow By default, logs are saved in the
/var/log/ipa/healthcheck/directory.- Save the file.
Ensure that the
crondservice is enabled and running:systemctl enable crond systemctl start crond
# systemctl enable crond # systemctl start crondCopy to Clipboard Copied! Toggle word wrap Toggle overflow To start generating logs, start the IdM healthcheck service:
systemctl start ipa-healthcheck
# systemctl start ipa-healthcheckCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
-
Navigate to the
/var/log/ipa/healthcheck/directory. - Display the contents of the log file to check if it was created correctly.
1.6. IdM Healthcheck configuration modifications Copiar o linkLink copiado para a área de transferência!
You can change Identity Management (IdM) Healthcheck settings by adding the desired command line options to the /etc/ipahealthcheck/ipahealthcheck.conf file. This can be useful when, for example, you configured log rotation previously and now want to ensure the logs are in a format suitable for automatic analysis, but do not want to set up a new timer.
This Healthcheck feature is only available on RHEL 8.7 and newer.
After the modification, all logs that Healthcheck creates follow the new settings. These settings also apply to any manual execution of Healthcheck.
When running Healthcheck manually, the settings in the configuration file take precedence over the options specified in the command line. For example, if output_type is set to human in the configuration file, specifying json on the command line has no effect. Any command line options you use that are not specified in the configuration file are applied normally.
1.7. Configuring Healthcheck to change the output logs format Copiar o linkLink copiado para a área de transferência!
Follow this procedure to configure Healthcheck with a timer already configured. In this example, you re-configure Healthcheck to start producing logs in a human-readable format and to also include successful results instead of only errors.
Prerequisites
- Your system is running RHEL 8.7 or later.
-
You have
rootprivileges. - You have previously configured log rotation on a timer.
Procedure
-
Open the
/etc/ipahealthcheck/ipahealthcheck.conffile in a text editor. -
Add options
output_type=humanandall=Trueto the[default]section. - Save and close the file.
Verification
Run Healthcheck manually:
ipa-healthcheck
# ipa-healthcheckCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
Go to
/var/log/ipa/healthcheck/and check that the logs are in the correct format.
Chapter 2. Checking services using IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
You can monitor services used by the Identity Management (IdM) server using the Healthcheck tool.
Prerequisites
- The Healthcheck tool is only available on RHEL 8.1 and newer
2.1. The IdM services Healthcheck test Copiar o linkLink copiado para a área de transferência!
The Healthcheck tool includes a test to check if the Identity Management (IdM) services are running correctly. Start with this Healthcheck test as IdM services that are not running correctly can cause failures in other Healthcheck tests.
The services test is context-specific based on what features are configured. For example, named is only checked if the integrated IdM DNS service is configured on the IdM server. Others, for example smb or winbind, are only checked if an IdM-AD trust is enabled.
The list of IdM services that the test evaluates can look as follows:
- certmonger
- dirsrv
- gssproxy
- httpd
- ipa_custodia
- ipa_dnskeysyncd
- ipa_otpd
- kadmin
- krb5kdc
- named
- pki_tomcatd
- sssd
You can view this list by running the ipa-healthcheck --list-sources command and identifying the ipahealthcheck.meta.services section in the output.
2.2. Screening IdM services using Healthcheck Copiar o linkLink copiado para a área de transferência!
Follow this procedure to run a standalone manual test of services running on the Identity Management (IdM) server by using the Healthcheck tool.
Procedure
Enter:
ipa-healthcheck --source=ipahealthcheck.meta.services
# ipa-healthcheck --source=ipahealthcheck.meta.servicesCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
The
--source=ipahealthcheck.meta.servicesoption ensures that IdM Healthcheck only performs the services test. -
The
--failures-onlyoption is enabled by default and it ensures that IdM Healthcheck only reports warnings, errors and critical issues.
A successful test displays empty brackets:
[ ]
[ ]Copy to Clipboard Copied! Toggle word wrap Toggle overflow If one of the services fails, the result can looks similarly to this example:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteRun this test on all IdM servers when trying to discover issues.
-
The
Chapter 3. Checking disk space using IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
You can monitor the Identity Management server’s free disk space using the Healthcheck tool.
Prerequisites
- The Healthcheck tool is only available on RHEL 8.1 and newer.
3.1. Disk space healthcheck test Copiar o linkLink copiado para a área de transferência!
The Healthcheck tool includes the FileSystemSpaceCheck test for checking available disk space. The test checks the following:
- The minimum raw free bytes needed.
- The percentage — the minimum free disk space is hardcoded to 20%.
The test checks the following paths:
| Paths checked by the test | Minimal disk space in MB |
|---|---|
|
| 1024 |
|
| 512 |
|
| 1024 |
|
| 512 |
|
| 512 |
|
| 512 |
Insufficient free disk space can cause issues with the following:
- Logging
- Execution
- Backups
You can find the FileSystemSpaceCheck test by running the ipa-healthcheck --list-sources command and identifying the ipahealthcheck.system.filesystemspace section in the output.
3.2. Screening disk space using the Healthcheck tool Copiar o linkLink copiado para a área de transferência!
Follow this procedure to run a standalone manual test of available disk space on an Identity Management (IdM) server using the Healthcheck tool.
Procedure
Enter:
ipa-healthcheck --source=ipahealthcheck.system.filesystemspace
# ipa-healthcheck --source=ipahealthcheck.system.filesystemspaceCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
The
--source=ipahealthcheck.meta.servicesoption ensures that IdM Healthcheck only performs the disk space test.
-
The
A successful test displays empty brackets:
[]
[]
As an example, a failed test can display:
This failed test informs you that no space is available in the /var/lib/dirsrv directory.
Run this test on all IdM servers when trying to discover issues.
Chapter 4. Verifying permissions of IdM configuration files using Healthcheck Copiar o linkLink copiado para a área de transferência!
Learn more about how to test Identity Management (IdM) configuration files using the Healthcheck tool.
Prerequisites
- The Healthcheck tool is only available on RHEL 8.1 or newer systems.
4.1. File permissions Healthcheck tests Copiar o linkLink copiado para a área de transferência!
The Healthcheck tool tests the ownership and permissions of files installed or configured by Identity Management (IdM).
If you change the ownership or permissions of these files, the tests return a warning in the result section. While this does not necessarily mean that the configuration does not work, it means that the file differs from the default configuration.
You can find the file permissions tests under the ipahealthcheck.ipa.files source of the output of the ipa-healthcheck --list-sources command.
- IPAFileNSSDBCheck
-
This test checks the 389-ds NSS database and the Certificate Authority (CA) database, if relevant. The 389-ds database is located in
/etc/dirsrv/slapd-<dashed-REALM>and the CA database is located in/etc/pki/pki-tomcat/alias/. - IPAFileCheck
This test checks the following files:
-
/var/lib/ipa/ra-agent.{key|pem} -
/var/lib/ipa/certs/httpd.pem -
/var/lib/ipa/private/httpd.key -
/etc/httpd/alias/ipasession.key -
/etc/dirsrv/ds.keytab -
/etc/ipa/ca.crt -
/etc/ipa/custodia/server.keys -
/etc/resolv.conf /etc/hostsIf PKINIT is enabled, it also tests:
-
/var/lib/ipa/certs/kdc.pem /var/lib/ipa/private/kdc.keyIf DNS is configured, it also tests:
-
/etc/named.keytab -
/etc/ipa/dnssec/ipa-dnskeysyncd.keytab
-
- TomcatFileCheck
This test checks certain
tomcat-specific files:-
/etc/pki/pki-tomcat/password.conf -
/var/lib/pki/pki-tomcat/conf/ca/CS.cfg -
/etc/pki/pki-tomcat/server.xml
-
4.2. Screening configuration files using Healthcheck Copiar o linkLink copiado para a área de transferência!
Follow this procedure to run a standalone manual test of an Identity Management (IdM) server’s configuration files using the Healthcheck tool.
The Healthcheck tool includes many tests. Results can be narrowed down by:
-
Including only ownership and permissions tests:
--source=ipahealthcheck.ipa.files
Procedure
To run Healthcheck tests on IdM configuration file ownership and permissions, while displaying only warnings, errors and critical issues, enter:
ipa-healthcheck --source=ipahealthcheck.ipa.files
# ipa-healthcheck --source=ipahealthcheck.ipa.filesCopy to Clipboard Copied! Toggle word wrap Toggle overflow
A successful test displays empty brackets:
ipa-healthcheck --source=ipahealthcheck.ipa.files
# ipa-healthcheck --source=ipahealthcheck.ipa.files
[]
Failed tests display results similar to the following WARNING:
Run these tests on all IdM servers when trying to find issues.
Chapter 5. Checking DNS records using IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
You can identify issues with DNS records in Identity Management (IdM) using the Healthcheck tool.
Prerequisites
- The DNS records Healthcheck tool is only available on RHEL 8.2 or newer.
5.1. DNS records healthcheck test Copiar o linkLink copiado para a área de transferência!
The Healthcheck tool includes the IPADNSSystemRecordsCheck test for checking that the expected DNS records required for autodiscovery are resolvable. Specifically, the test checks the DNS records obtained by the ipa dns-update-system-records --dry-run command using the first resolver specified in the /etc/resolv.conf file on the IdM server to which you are logged in.
You can find the IPADNSSystemRecordsCheck test under the ipahealthcheck.ipa.idns source of the output of the ipa-healthcheck --list-sources command.
5.2. Screening IdM DNS records using the Healthcheck tool Copiar o linkLink copiado para a área de transferência!
Follow this procedure to run a standalone manual test of DNS records on an Identity Management (IdM) server using the Healthcheck tool.
The Healthcheck tool includes many tests. Results can be narrowed down by including only the DNS records tests by adding the --source ipahealthcheck.ipa.idns option.
Prerequisites
-
You have
rootprivileges.
Procedure
Enter:
ipa-healthcheck --source ipahealthcheck.ipa.idns
# ipa-healthcheck --source ipahealthcheck.ipa.idnsCopy to Clipboard Copied! Toggle word wrap Toggle overflow The
--source ipahealthcheck.ipa.idnsoption ensures that IdM Healthcheck only performs the DNS records test.If the record is resolvable, the test returns
SUCCESSas a result:Copy to Clipboard Copied! Toggle word wrap Toggle overflow The test returns a
WARNINGwhen, for example, the number of records does not match the expected number:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 6. Verifying the optimal number of KDC worker processes using IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
You can use the Healthcheck tool in Identity Management (IdM) to verify that the Kerberos Key Distribution Center (KDC) is configured to use the optimal number of krb5kdc worker processes, which should be equal to the number of CPU cores on the host.
Prerequisites
- You are using RHEL 8.7 or later.
-
You have
rootprivileges.
Procedure
Enter:
ipa-healthcheck --source ipahealthcheck.ipa.kdc
# ipa-healthcheck --source ipahealthcheck.ipa.kdcCopy to Clipboard Copied! Toggle word wrap Toggle overflow The
--source ipahealthcheck.ipa.kdcoption ensures that IdM Healthcheck only performs theKDCWorkersChecktest.If the number of KDC worker processes matches the number of CPU cores, the test returns
SUCCESSas a result:Copy to Clipboard Copied! Toggle word wrap Toggle overflow The test returns a
WARNINGif the number of worker processes does not match the number of CPU cores. In the following example, a host with 2 cores is configured to have only one KDC worker process:Copy to Clipboard Copied! Toggle word wrap Toggle overflow The test also outputs a
WARNINGif there are no configured workers. In the following example, theKRB5KDC_ARGSvariable is missing from the/etc/sysconfig/krb5kdcconfiguration file:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 7. Checking IdM replication using Healthcheck Copiar o linkLink copiado para a área de transferência!
You can test Identity Management (IdM) replication using the Healthcheck tool.
Prerequisites
- You are using RHEL version 8.1 or newer.
7.1. The IdM replication and topology Healthcheck tests Copiar o linkLink copiado para a área de transferência!
The Healthcheck tool includes tests of the Identity Management (IdM) topology configuration. The tests search for replication conflict issues.
You can find the IPATopologyDomainCheck and ReplicationConflictCheck tests under the ipahealthcheck.ipa.topology and ipahealthcheck.ds.replication sources of the output of the ipa-healthcheck --list-sources command.
- IPATopologyDomainCheck
Tests the following configuration:
- No IdM server is disconnected from the topology.
- The IdM servers do not have more than the recommended number of replication agreements.
If the test succeeds, the test returns the configured domains. Otherwise, specific connection errors are reported.
NoteThe test runs the
ipa topologysuffix-verifycommand for thedomainsuffix. It also runs the command for thecasuffix if the IdM Certificate Authority server role is configured on this server.- ReplicationConflictCheck
-
Searches for entries in LDAP matching
(&(!(objectclass=nstombstone))(nsds5ReplConflict=*)).
7.2. Screening replication using Healthcheck Copiar o linkLink copiado para a área de transferência!
Follow this procedure to run a standalone manual test of your Identity Management (IdM) replication and topology configuration using the Healthcheck tool.
Prerequisites
-
You have
rootprivileges.
Procedure
Enter:
ipa-healthcheck --source=ipahealthcheck.ds.replication --source=ipahealthcheck.ipa.topology
# ipa-healthcheck --source=ipahealthcheck.ds.replication --source=ipahealthcheck.ipa.topologyCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
The
--source=ipahealthcheck.ds.replicationand--source=ipahealthcheck.ipa.topologyoptions ensure that IdM Healthcheck only performs the replication conflict and topology tests.
Four different results are possible:
SUCCESS — the test passed successfully.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - WARNING — the test passed but there might be a problem.
ERROR — the test failed.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - CRITICAL — the test failed and it affects the IdM server functionality.
-
The
Run these tests on all IdM servers when trying to check for issues.
7.3. Additional resources Copiar o linkLink copiado para a área de transferência!
Chapter 8. Verifying your IdM and AD trust configuration using IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
Learn more about identifying issues with a trust between Identity Management (IdM) and Active Directory (AD) by using the Healthcheck tool.
Prerequisites
- The Healthcheck tool is only available on RHEL 8.1 or newer
8.1. IdM and AD trust Healthcheck tests Copiar o linkLink copiado para a área de transferência!
The Healthcheck tool includes several tests for testing the status of the trust between Identity Management (IdM) and Active Directory (AD).
To see all trust tests, run ipa-healthcheck with the --list-sources option:
ipa-healthcheck --list-sources
# ipa-healthcheck --list-sources
You can find all trust-related tests under the ipahealthcheck.ipa.trust source:
- IPATrustAgentCheck
-
This test checks the SSSD configuration if the current host is configured as a trust agent. For each domain in
/etc/sssd/sssd.confwhereid_provider=ipaensure thatipa_server_modeisTrue. - IPATrustDomainsCheck
-
This test checks if the trust domains match SSSD domains by comparing the list of domains in
sssctl domain-listwith the list of domains fromipa trust-findexcluding the IdM domain. - IPATrustCatalogCheck
This test resolves an AD user,
Administrator@REALM. This populates the AD Global catalog and AD Domain Controller values insssctl domain-statusoutput.For each trust domain look up the user with the ID of the SID + 500, that is the administrator ID, and then check the output of
sssctl domain-status <domain> --active-serverto ensure that the domain is active.- IPAsidgenpluginCheck
-
This test verifies that the
sidgenplugin is enabled in the IdM 389-ds instance. The test also verifies that theIPA SIDGENandipa-sidgen-taskplugins incn=plugins,cn=configinclude thensslapd-pluginEnabledoption. - IPATrustAgentMemberCheck
-
This test verifies that the current host is a member of
cn=adtrust agents,cn=sysaccounts,cn=etc,SUFFIX. - IPATrustControllerPrincipalCheck
-
This test verifies that the current host is a member of
cn=adtrust agents,cn=sysaccounts,cn=etc,SUFFIX. - IPATrustControllerServiceCheck
- This test verifies that the current host starts the ADTRUST service in ipactl.
- IPATrustControllerConfCheck
-
This test verifies that
ldapiis enabled for the passdb backend in the output ofnet conflist. - IPATrustControllerGroupSIDCheck
-
This test verifies that the
adminsgroup’s SID ends with 512, which is the Domain Admins' RID. - IPATrustPackageCheck
-
This test verifies that the
trust-adpackage is installed if the trust controller and AD trust are not enabled.
8.2. Screening the trust with the Healthcheck tool Copiar o linkLink copiado para a área de transferência!
Follow this procedure to run a standalone manual test of an Identity Management (IdM) and Active Directory (AD) trust health check using the Healthcheck tool.
Procedure
Enter:
ipa-healthcheck --source=ipahealthcheck.ipa.trust --failures-only
# ipa-healthcheck --source=ipahealthcheck.ipa.trust --failures-onlyCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
The
--source=ipahealthcheck.ipa.trustoption ensures that IdM Healthcheck only performs the trust tests.
-
The
Successful test displays empty brackets:
ipa-healthcheck --source=ipahealthcheck.ipa.trust
# ipa-healthcheck --source=ipahealthcheck.ipa.trust
[]
Run these tests on all IdM servers when trying to find an issue.
Chapter 9. Verifying system certificates using IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
Learn more about identifying issues with system certificates in Identity Management (IdM) by using the Healthcheck tool.
Prerequisites
- The Healthcheck tool is only available on RHEL 8.1 or newer.
9.1. System certificates Healthcheck tests Copiar o linkLink copiado para a área de transferência!
The Healthcheck tool includes several tests for verifying system, or Dogtag, certificates.
You can find all certificate-related tests under the ipahealthcheck.dogtag.ca source in the output of the ipa-healthcheck --list-sources command.
- DogtagCertsConfigCheck
This test compares the CA (Certificate Authority) certificates in its NSS database to the same values stored in
CS.cfg. If they do not match, the CA fails to start.Specifically, it checks:
-
auditSigningCert cert-pki-caagainstca.audit_signing.cert -
ocspSigningCert cert-pki-caagainstca.ocsp_signing.cert -
caSigningCert cert-pki-caagainstca.signing.cert -
subsystemCert cert-pki-caagainstca.subsystem.cert -
Server-Cert cert-pki-caagainstca.sslserver.cert
If Key Recovery Authority (KRA) is installed, it also checks:
-
transportCert cert-pki-kraagainstca.connector.KRA.transportCert
-
- DogtagCertsConnectivityCheck
This test verifies connectivity. This test is equivalent to the
ipa cert-show 1command which checks the following:- The PKI proxy configuration in Apache
- IdM being able to find a CA
- The RA agent client certificate
- The correctness of CA replies to requests
The test verifies that the
ipa cert-showcommand can be executed and that an expected response is returned from the IdM CA - either the certificate itself or anot foundresponse.
9.2. Screening system certificates using Healthcheck Copiar o linkLink copiado para a área de transferência!
Follow this procedure to run a standalone manual test of Identity Management (IdM) certificates using the Healthcheck tool.
Procedure
Enter:
ipa-healthcheck --source=ipahealthcheck.dogtag.ca
# ipa-healthcheck --source=ipahealthcheck.dogtag.caCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
The
--source=ipahealthcheck.dogtag.caoption ensures that Healthcheck only performs the certificate tests.
-
The
An example of a successful test:
An example of a failed test:
Run the certificate tests on all IdM servers when trying to find an issue.
Chapter 10. Verifying certificates using IdM Healthcheck Copiar o linkLink copiado para a área de transferência!
Learn more about understanding and using the Healthcheck tool in Identity management (IdM) to identify issues with IdM certificates maintained by the certmonger utility.
Prerequisites
- The Healthcheck tool is only available in RHEL 8.1 and newer.
10.1. IdM certificates Healthcheck tests Copiar o linkLink copiado para a área de transferência!
The Healthcheck tool includes several tests for verifying the status of certificates maintained by certmonger in Identity Management (IdM). For details about certmonger, see Obtaining an IdM certificate for a service using certmonger.
This suite of tests checks certificate expiration, validation, trust, and other configuration. Healthcheck can report multiple errors for the same underlying issue.
You can find these certificate tests under the ipahealthcheck.ipa.certs source in the output of the ipa-healthcheck --list-sources command.
- IPACertmongerExpirationCheck
This test checks expirations in
certmonger.If an error is reported, the certificate has expired.
If a warning appears, the certificate expires soon. By default, a warning appears if the test is run 28 days or fewer before certificate expiration.
You can configure the number of days in the
/etc/ipahealthcheck/ipahealthcheck.conffile. After opening the file, change thecert_expiration_daysoption located in thedefaultsection.NoteCertmongerloads and maintains its own view of the certificate expiration. This check does not validate the on-disk certificate.- IPACertfileExpirationCheck
This test checks if the certificate file or NSS database have correct access rights configured. This test also checks expiration. Therefore, carefully read the
msgattribute in the error or warning output. The message specifies the problem.NoteThis test checks the on-disk certificate. If a certificate is missing or unreadable, Healthcheck returns an error.
- IPACertNSSTrust
- This test analyzes the trust for certificates stored in the NSS databases. For the expected tracked certificates in the NSS databases, Healthcheck compares the trust to an expected value and raises an error on a non-match.
- IPANSSChainValidation
-
This test validates the certificate chain of the NSS certificates. The test executes the
certutil -V -u V -e -d [dbdir] -n [nickname]command. - IPAOpenSSLChainValidation
This test validates the certificate chain of the OpenSSL certificates. Specifically, Healthcheck executes the following OpenSSL command:
openssl verify -verbose -show_chain -CAfile /etc/ipa/ca.crt [cert file]
openssl verify -verbose -show_chain -CAfile /etc/ipa/ca.crt [cert file]Copy to Clipboard Copied! Toggle word wrap Toggle overflow - IPARAAgent
-
This test compares the certificate on disk with the equivalent record in LDAP in
uid=ipara,ou=People,o=ipaca. - IPACertRevocation
-
This test verifies that certificates that are maintained by
certmongerhave not been revoked. - IPACertmongerCA
This test verifies the
certmongerCertificate Authority (CA) configuration. IdM cannot issue certificates without a CA.Certmongermaintains a set of CA helpers. A CA namedIPAissues certificates for hosts or services through IdM, authenticating as a host or user principal.There are also
dogtag-ipa-ca-renew-agentanddogtag-ipa-ca-renew-agent-reusethat renew the CA subsystem certificates.
10.2. Screening certificates using the Healthcheck tool Copiar o linkLink copiado para a área de transferência!
Follow this procedure to run a standalone manual test of an Identity Management (IdM) certificate health check using the Healthcheck tool.
Prerequisites
-
You have
rootprivileges.
Procedure
Enter:
ipa-healthcheck --source=ipahealthcheck.ipa.certs --failures-only
# ipa-healthcheck --source=ipahealthcheck.ipa.certs --failures-onlyCopy to Clipboard Copied! Toggle word wrap Toggle overflow The
--source=ipahealthcheck.ipa.certsoption ensures that IdM Healthcheck only performs thecertmongercertificate tests.Successful test displays empty brackets:
[]
[]Copy to Clipboard Copied! Toggle word wrap Toggle overflow Failed test shows you the following output:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
This
IPACertfileExpirationChecktest failed on opening the NSS database.
Run this suite of Healthcheck tests on all IdM servers when trying to check for issues.