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.
Bug 1358457 - ipa installer SecurityWarning certificate has no subjectAltName
Summary: ipa installer SecurityWarning certificate has no subjectAltName
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
Aneta Šteflová Petrová
Depends On:
Blocks: 1420851 1477664
TreeView+ depends on / blocked
Reported: 2016-07-20 18:12 UTC by Scott Poore
Modified: 2021-06-10 11:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Security warning when using "ipa-kra-install", "ipa-ca-install", or "ipa-replica-install" When using the "ipa-kra-install", "ipa-ca-install", and "ipa-replica-install" utilities to install an additional key recovery authority (KRA) component, certificate authority, or replica, the following warning appears: SecurityWarning: Certificate has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. The error occurs due to RFC 2818, which deprecates the practice of carrying the subject host name in the subject distinguished name (DN) common name (CN) field. However, the three utilities succeed. Therefore, you can ignore the warning message.
Clone Of:
Last Closed: 2018-10-15 11:23:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Scott Poore 2016-07-20 18:12:58 UTC
Description of problem:

When Installing a second KRA on an IPA Replica, I see this warning:

/usr/lib/python2.7/site-packages/urllib3/connection.py:251: SecurityWarning: Certificate has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
on Master:
1.  ipa-server-install
2.  ipa-kra-install
on Replica:
3.  ipa-replica-install
4.  ipa-ca-install
5.  ipa-kra-install

Actual results:
appears to work but, throws above warning

Expected results:
No warning was expected so I'm raising this here.

Additional info:

If this is a non-issue, we may still want to document this as expected behavior in release notes.

Comment 2 Scott Poore 2016-07-20 18:36:35 UTC
FYI, I saw the same on ipa-ca-install and ipa-replica-install.  I missed that before but, looking back through an install, I do see it in both places as well.

Comment 4 Petr Vobornik 2016-08-06 12:12:28 UTC
Upstream ticket:

Comment 9 Florence Blanc-Renaud 2018-10-15 11:23:22 UTC
This issue was fixed with the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1562423 SAN in internal SSL server certificate in pkispawn configuration step
The fix was done on 7.6 and backported to 7.5 z-stream.


Note You need to log in before you can comment on or make changes to this bug.