Description of problem:
On Satellite 6 server, if the SmartCard is inserted, the Red Hat Satellite Server web authentication page tries to use it, and will not allow normal LDAP authentication. on Macs it seems as if the web page tries to use Kerberos authentication.
Also, even if the user has already successfully authenticated via LDAP before inserting the SmartCard, again it tries to use SmartCard authentication.
Firefox and Safari on Red Hat Enterprise Linux 6.7 and 7.2
Mac OS X 10.10
If the SmartCard is inserted, the Red Hat Satellite Server web authentication page tries to use it, and will not allow normal LDAP authentication.
also, if already authenticated successfully, the current Satellite page stays up when smart card is inserted, but as soon as an attempt is made to navigate to another page on Satellite, the smart card prompt appears
When SmartCard is inserted, the Red Hat Satellite Server web authentication page tries to use it, and will not allow normal LDAP authentication.
Satellite Web UI should not try to use smartcard authentication.
Moving 6.2 bugs out to sat-backlog.
Could you please let us know, how the satellite was installed? Was it configured to allow external authentication using IDM as described at https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/User_Guide/sect-Red_Hat_Satellite-User_Guide-Configuring_External_Authentication-Using_Identity_Management.html ? Or is the LDAP authentication, which was mentioned in the report, configured via External Auth source as described in https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/User_Guide/chap-Red_Hat_Satellite-User_Guide-Configuring_External_Authentication.html#sect-Red_Hat_Satellite-User_Guide-Using_LDAP ?
Additionaly please check with the customer whether they modified any file under /etc/httpd manually and ask them to send all files from there in a tarball.
Also please ask them what is the value of security.default_personal_cert in about:config in their Firefox.
It might also help if they append their smart card vendor CA to /etc/pki/katello/certs/katello-default-ca.crt, after restarting the Apache, we could trust client certificate but it wouldn't be used for authentication. If they experiment with this, make sure they make a backup before they start.
By default we set SSLVerifyClient to optional so it can be used on some URLs where we authenticate capsules using x509 certificates. For some reason, the certificate from smart card is used by the client and the authentication fails because Apache is not configured to trust the issuer.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.