The eduPerson object class appears to be using an outdated revision: http://www.internet2.edu/media/medialibrary/2013/09/04/internet2-mace-dir-eduperson-201203.html
There have been a couple of new revisions since: http://software.internet2.edu/eduperson/internet2-mace-dir-eduperson-201310.html http://software.internet2.edu/eduperson/internet2-mace-dir-eduperson-201602.html
Currently having to store newly added attributes (eduPersonUniqueId, in particular) in a custom object class as a workaround.
Attaching the ldif currently packaged and released.
CentOS release 6.8 (Final) vendorVersion: 389-Directory/1.2.11.15 B2017.011.1820 Linux 2.6.32-642.15.1.el6.x86_64 #1 SMP Fri Feb 24 14:31:22 UTC 2017
N/A
<img alt="60eduperson.ldif" src="/389-ds-base/issue/raw/files/4ab49ae052d689bc2a40dfc8aeaf074dbfaf4c128f997111570baed5fbad4baf-60eduperson.ldif" />
Metadata Update from @firstyear: - Issue assigned to firstyear
Metadata Update from @mreynolds: - Custom field type adjusted to defect - Issue set to the milestone: 1.3.7 backlog
<img alt="0001-Ticket-49248-update-eduPerson-to-201602.patch" src="/389-ds-base/issue/raw/files/7fb2468de126137993f72dc31bc11668eae91f161dd7948724a6078595557525-0001-Ticket-49248-update-eduPerson-to-201602.patch" />
@scellef Can you please confirm this schema definition is correct as well? I took care in updating it but I want to be sure it's valid. Thanks!
Looks good to me!
@mreynolds Can you please review this for me?
Looks good, ack. I wonder if we have other schema that is outdated? Perhaps we should open a new ticket for that to be investigated (I think that would be a good candidate for 1.3.7 as well)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: review)
commit 063b367 To ssh://git@pagure.io/389-ds-base.git 613e871..063b367 master -> master
Yeah, it's a good idea. I just thinking it's hard to know what is or isn't outdated ...
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
<img alt="0001-Fixes-49248-Add-docstring-for-eduPerson-standard-obj.patch" src="/389-ds-base/issue/raw/files/ed7c1909d204071007715efdab2ecef4053522e85c3b66890cd6f66af015cadf-0001-Fixes-49248-Add-docstring-for-eduPerson-standard-obj.patch" />
Fix the commit message, please.
Issue 49248 - Add a docstring to test case https://pagure.io/389-ds-base/issue/49248 Reviewed by: ?
Metadata Update from @spichugi: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field version adjusted to None
<img alt="0001-Issue-49248-Added-a-docstring-to-account-locking-tes.patch" src="/389-ds-base/issue/raw/files/a69f4c906605d54b7a8c8414bbe1a4c419d6a57965915b910c1a151f77d9aeab-0001-Issue-49248-Added-a-docstring-to-account-locking-tes.patch" />
<img alt="0001-Issue-49248-Add-a-docstring-to-account-locking-test-.patch" src="/389-ds-base/issue/raw/files/07c67e115b4097057410621accace04fb61a33b4c2f3ca6f44e2ae611d675a72-0001-Issue-49248-Add-a-docstring-to-account-locking-test-.patch" />
commit c3da727 Author: Akshay Shivekar ashiveka@redhat.com Date: Thu Aug 17 15:17:08 2017 +0530
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/2307
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.