Bug 1117920 - user creation allowed via gui during kickstart install
Summary: user creation allowed via gui during kickstart install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-09 16:00 UTC by Ross Smith
Modified: 2014-07-23 20:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-23 20:25:44 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ross Smith 2014-07-09 16:00:53 UTC
Description of problem:
When performing a kickstart installation, if a user is not created in the kickstart file, the option to create a user is available.  Once a user is created in the gui the option is then locked and cannot be modified.  

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

How reproducible:
Always

Steps to Reproduce:
1.Perform kickstart install specifying root password but not creating a user
2.Complete summary hub 
3.click to continue installation

Actual results:
Can access the create user spoke to create a user but it's locked once one is created.

Expected results:
user account creation locked or unlocked completely. 

Additional info:
I'd prefer it to be locked as that's more secure, but I can see the argument the other way.  Perhaps a way to specify what things should be locked in the kickstart file would be helpful in the future.

Comment 2 David Cantrell 2014-07-23 20:01:29 UTC
devel_ack- for RHEL-7.  I understand the request, but this change is more appropriately worked upstream in Fedora where we can do a proper UX design and assessment and implementation.

Comment 3 RHEL Program Management 2014-07-23 20:25:44 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.


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