Bug 707590

Summary:	Authconfig should warn of incorrect URI syntax for literal IPv6 addresses
Product:	Red Hat Enterprise Linux 6	Reporter:	Stephen Gallagher <sgallagh>
Component:	authconfig	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED ERRATA	QA Contact:	David Spurek <dspurek>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1	CC:	dspurek, ebenes, jlieskov, mnavrati, ohudlick, pvrabec, salmy, yjog
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	authconfig-6.1.12-16.el6	Doc Type:	Enhancement
Doc Text:	No docs needed	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-14 07:44:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	947781

Description Stephen Gallagher 2011-05-25 13:20:10 UTC

Description of problem:
http://www.ietf.org/rfc/rfc2732.txt requires that URIs containing a literal IPv6 address must have the address wrapped in brackets in order to differentiate the end of the address from the optionally-specified port.

Right now, it is possible to specify:
ldap://fc00::126:25
in authconfig without error or warning. This URI will be unusable for either nss_ldap or SSSD (as it will fail to parse).

Authconfig should validate that a URI is valid under RFC 2732. Probably the best way to accomplish this would be to pass the provider LDAP URIs into the python urlparse library for validation.

It should not be permissible to save a configuration for which urlparse returns an error.

Version-Release number of selected component (if applicable):
authconfig-6.1.12-5.el6

Comment 2 RHEL Program Management 2011-07-06 01:31:48 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 RHEL Program Management 2012-05-03 05:14:04 UTC

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2013-10-14 01:05:19 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 14 errata-xmlrpc 2014-10-14 07:44:17 UTC

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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1558.html