RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_identity_management/configuring-idm-for-smart-card-auth_configuring-and-managing-idm

Section Number and Name:
39.1. Configuring the IdM server for smart card authentication
39.2. Configuring the IdM client for smart card authentication

Describe the issue:
 
Smartcard scripts generated by ipa-advise must have CAs provided in their argument list. The scripts will fail to complete if either of the following occurs:
1) sub root CAs appear in the argument list before their root CAs
2) any CA is expired, aborting the script and not processing any other CAs on the command line

Suggestions for improvement:
The documentation should clearly state that the root CAs must be provided on the command line before any sub root CAs and that no CA can be expired (or expire within the time necessary to run the script)

Additional information: 
I created a script at https://gitlab.cee.redhat.com/rlucente/idm-dod-cac-auth that downloads US Department of Defense CAs, breaks out CAs into individual PEM files, performs sanity checks, then presents the CAs to the ipa-advise generated scripts in the proper order.