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 720459

Summary: Sudo Schema is old and needs updating
Product: Red Hat Enterprise Linux 6 Reporter: Rich Megginson <rmeggins>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Chandrasekar Kannan <ckannan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2CC: amsharma, benl, jgalipea, jr.aquino, shaines
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 389-ds-base-1.2.8.6-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 713209 Environment:
Last Closed: 2011-12-06 17:55:36 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:
Bug Depends On: 713209    
Bug Blocks: 690318    

Comment 5 Jenny Severance 2011-09-23 17:14:58 UTC
You just need to verify that the following
attributes are defined in the schema after setting up a DS instance:

  sudoRunAsUser
  sudoRunAsGroup
  sudoNotBefore
  sudoNotAfter
  sudoOrder

You can check the schema by either grepping the schema files for these
attributes in /etc/dirsrv/slapd-<instance>/schema, or you can use ldapsearch to
return the loaded schema by searching the 'cn=schema' entry and explicitly
requesting the 'attributeTypes' attribute to be returned.  You can then grep
through the returned values for the attribute definitions mentioned above.

Comment 6 Jenny Severance 2011-09-27 18:44:46 UTC
verified :

# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoRunAsUser
  NAME 'sudoRunAsUser'
  MAY ( sudoUser $ sudoHost $ sudoCommand $ sudoRunAs $ sudoRunAsUser $

# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoRunAsGroup
  NAME 'sudoRunAsGroup'
        sudoRunAsGroup $ sudoOption $ sudoNotBefore $ sudoNotAfter $

# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoNotBefore
   NAME 'sudoNotBefore'
        sudoRunAsGroup $ sudoOption $ sudoNotBefore $ sudoNotAfter $

# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoNotAfter
  NAME 'sudoNotAfter'
        sudoRunAsGroup $ sudoOption $ sudoNotBefore $ sudoNotAfter $
# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoOrder
  NAME 'sudoOrder'
        sudoOrder $ description )

version:
389-ds-base-1.2.9.11-1.el6.x86_64

Comment 7 errata-xmlrpc 2011-12-06 17:55:36 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/RHEA-2011-1711.html