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.

Bug 719922

Summary:	Connection profile is created even if admin authentication fails or is canceled
Product:	Red Hat Enterprise Linux 6	Reporter:	Jiri Koten <jkoten>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED NOTABUG	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.1	CC:	rkhan, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-19 18:13:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Koten 2011-07-08 12:36:48 UTC

Description of problem:
If creation of Ad-Hoc network is restricted (see bug 705806) and the required authentication fails, the connection profile is still created and present in NM connection editor. It's created even when creation is not allowed at all. 

Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-9.el6_1.1

How reproducible:
100%

Steps to Reproduce:
1. Modify
/usr/share/polkit-1/actions/org.freedesktop.network-manager-settings.system.policy
line 299 from:
<allow_active>any</allow_active>
to:
<allow_active>auth_admin</allow_active>
2.  Create an insecure wireless network by clicking on the nm-applet, go to
Create New Wireless Network
Network name: test
Wireless security: none
Hit Create
3. When authentication dialog appears enter wrong passwd or hit cancel.
4. Open nm-connection-editor  
  
Actual results:
Connection profile "test" is present.

Expected results:
No profile is created.

Comment 1 RHEL Program Management 2011-10-07 16:00:18 UTC

Since RHEL 6.2 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 2 Dan Williams 2013-02-19 18:13:14 UTC

Yes, the profile is created, but the user is never able to start that wifi network; they are always denied when they attempt to do so.  To prevent the user from changing any network connections, the "system.modify" permission can be changed for that user.