#51034 389ds misses the labeledURIObject Object Class from RFC2079
Closed: wontfix 3 years ago by mreynolds. Opened 4 years ago by minfrin.

Issue Description

https://tools.ietf.org/html/rfc2079 defines the labeledURIObject objectclass, however this is missing from 389ds.

The attribute labeledURI from rfc2079 is present, but limited to inetOrgPerson only.

Package Version and Platform

389-ds-base-1.3.9.1-13.el7_7.x86_64

Steps to reproduce

  1. Install 389ds
  2. Try access labeledURIObject

Actual results

Objectclass is missing.

Expected results

Objectclass is present.


This should be pretty easy to add, but I'd want to check with @mreynolds if we would back port this to 1.3.x.

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

4 years ago

Metadata Update from @mreynolds:
- Issue priority set to: major
- Issue set to the milestone: 1.4.3

4 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.4 (was: 1.4.3)

4 years ago

Sorry about the delay on this. I don't think we'll backport this but you should easily be able to add the schema to your 99user.ldif for now.

https://pagure.io/389-ds-base/pull-request/51130

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/4087

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata