Bug 1115048

Summary: Description attribute should not be required
Product: Red Hat Enterprise Linux 7 Reporter: Dmitri Pal <dpal>
Component: ipaAssignee: Martin Kosek <mkosek>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0CC: rcritten, spoore
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.1.0-0.1.alpha1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 10:14:53 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 Dmitri Pal 2014-07-01 13:19:09 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4387

LDAP attribute `description` (OID `2.5.4.13`) is always optional in LDAP schema but IPA UI forces user to enter something.

I have noticed this problem with `permission-add`, `privilege-add` and `role-add` commands but I suspect that the same applies to many other IPA commands.

Comment 3 Scott Poore 2015-01-28 01:52:02 UTC
verified.

Version ::

ipa-server-4.1.0-16.el7.x86_64

Results ::

Tested successfully in WebUI.

[root@vm8 ~]# ipa role-add testrole1
----------------------
Added role "testrole1"
----------------------
  Role name: testrole1

[root@vm8 ~]# ipa privilege-add testpriv1
---------------------------
Added privilege "testpriv1"
---------------------------
  Privilege name: testpriv1

[root@vm8 ~]# ipa permission-add --right=read --bindtype=permission --subtree="dc=ipa2,dc=example,dc=com" --target="cn=dns,dc=ipa2,dc=example,dc=com" testperms1
-----------------------------
Added permission "testperms1"
-----------------------------
  Permission name: testperms1
  Granted rights: read
  Bind rule type: permission
  Subtree: dc=ipa2,dc=example,dc=com
  Target DN: cn=dns,dc=ipa2,dc=example,dc=com

Comment 5 errata-xmlrpc 2015-03-05 10:14:53 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.

https://rhn.redhat.com/errata/RHSA-2015-0442.html