Bug 834046 - [RFE] Add nsTLS1 attribute to schema and objectclass nsEncryptionConfig
[RFE] Add nsTLS1 attribute to schema and objectclass nsEncryptionConfig
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Rich Megginson
Sankar Ramalingam
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2012-06-20 13:50 EDT by Nathan Kinder
Modified: 2013-02-21 03:18 EST (History)
3 users (show)

See Also:
Fixed In Version: 389-ds-base-
Doc Type: Enhancement
Doc Text:
Feature: Schema Reason: needed to update schema for DS config settings Result (if any):
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 03:18:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nathan Kinder 2012-06-20 13:50:45 EDT
This bug is created as a clone of upstream ticket:


The ssl.c code will use the attribute nsTLS1 if defined, but there is no such
attribute defined by the schema, nor will nsEncryptionConfig allow it.  We need
to add this attribute to the schema and to objectclass nsEncryptionConfig.
Comment 1 Jenny Galipeau 2012-06-22 14:47:53 EDT
please add steps to verify this issue and how the attribute should be verified functionally
Comment 2 Noriko Hosoi 2012-07-09 19:18:21 EDT
Added a test case bug834046 to acceptance - schema.
Comment 4 Jenny Galipeau 2013-01-14 10:00:34 EST
verified ::

200|0 24 15:19:11|TP Start
520|0 24 31128 1 1|bug834046: Add nsTLS1 attribute to schema and objectclass nsEncryptionConfig
520|0 24 31128 1 2|bug834046: attrybuteTypes
520|0 24 31128 1 3|bug834046: attrybuteTypes nsTLS1 exists: OK
520|0 24 31128 1 4|bug834046: objectClasses
520|0 24 31128 1 5|bug834046: objectClasses nsTLS1 exists: OK
520|0 24 31128 1 6|TestCase [bug834046] result-> [PASS]

version :: 389-ds-base-
Comment 6 errata-xmlrpc 2013-02-21 03:18:17 EST
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.


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