Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionThorsten Scherf
2021-05-12 09:37:00 UTC
Description of problem:
Version-Release number of selected component (if applicable):
This is about ipa-advise script. In our docs [1] we ask customers to run the following sequence of commands to generate an ipa-advise script that they can then execute on their clients:
# ipa-advise config-client-for-smart-card-auth > client_smart_card_script.sh # then copy the script to the client
# chmod +x client_smart_card_script.sh
# ./client_smart_card_script.sh CA_cert.pem
The script then uses the following code to check if OpenSC module is already loaded and in case it's not it loads the module:
systemctl start pcscd.service pcscd.socket && systemctl enable pcscd.service pcscd.socket
if modutil -dbdir /etc/pki/nssdb -list | grep -q OpenSC
then
echo "OpenSC PKCS#11 module already configured"
else
echo "" | modutil -dbdir /etc/pki/nssdb -add "OpenSC" -libfile /usr/lib64/opensc-pkcs11.so
fi
The problem is that the OpenSC module is managed by p11-kit (since rhel-8.1 iirc) and is not directly loaded by modutil anymore. As a result, when the script is executed, the following error pops up:
ERROR: Failed to add module "OpenSC". Probable cause : "Unknown PKCS #11 error.".
This is confusing and should be avoided. It's clear that the script is also used on non RHEL machines where p11-kit might not be available, there I would recommend to conditionally run the command based on the environment where the script is executed.
[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/system_design_guide/configuring-applications-to-use-cryptographic-hardware-through-pkcs-11_system-design-guide
Expected results:
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Additional info:
Once p11-kit has loaded the OpenSC module, it shows up (together with the token when available) in the 'p11-kit list-modules' output but not in 'modutil -dbdir /etc/pki/nssdb -list' output.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (idm:client and idm:DL1 bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2022:1884
Comment 26Red Hat Bugzilla
2023-09-15 01:34:01 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days