Bug 742024

Summary:	[ipa webui] Missing option in Config tab to set default shell
Product:	Red Hat Enterprise Linux 6	Reporter:	Namita Soman <nsoman>
Component:	ipa	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED ERRATA	QA Contact:	IDM QE LIST <seceng-idm-qe-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	bcook, dpal, edewata, jgalipea, mkosek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ipa-2.1.2-1.el6	Doc Type:	Bug Fix
Doc Text:	Do not document	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 18:32:56 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 Namita Soman 2011-09-28 19:46:46 UTC

Description of problem:
ipa config-mod allows
--defaultshell=STR    Default shell for new users.

But this setting is not available in UI 

Version-Release number of selected component (if applicable):
ipa-server-2.1.1-4.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. ipa help config-mod
2. this lists - --defaultshell=STR    Default shell for new users.
3. In UI, go to Configuration tab
  
Actual results:
no option to set a new user's default shell

Expected results:
option to set new user's default shell

Additional info:

Comment 2 Dmitri Pal 2011-09-28 21:40:07 UTC

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1895

Comment 5 Namita Soman 2011-10-11 14:17:30 UTC

Verified using ipa-server-2.1.2-2.el6.x86_64
Can set Default shell in Configuration UI

Comment 6 Martin Kosek 2011-11-01 08:17:57 UTC

Not present in 6.1

Comment 7 Martin Kosek 2011-11-01 08:17:58 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Do not document

Comment 8 errata-xmlrpc 2011-12-06 18:32:56 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/RHSA-2011-1533.html