Impossible to use createTimestamp as a column in manager interface
Impossible to use createTimestamp as a column in manager interface
Description
Impossible to use createTimestamp as a column in manager interface
Distribution Name and Version
Debian
FusionDirectory Version
1.4-dev
PHP version used
PHP7
Origin of php packages
Debian
Steps to Reproduce
- Try to add a column createTimestamp in manager interface
- The column is empty
Expected behavior:
A column with the date
Actual behavior:
Column is empty
Reproduces how often: 100%
Link issues together to show that they're related. Learn more.
Activity
- bmortier changed milestone to %FusionDirectory 1.4
changed milestone to %FusionDirectory 1.4
By Jonathan Swaelens on 2019-09-12T12:09:12 (imported from GitLab)
- bmortier added PJ1811-0242 label
added PJ1811-0242 label
- bmortier changed due date to September 15, 2019
changed due date to September 15, 2019
By bmortier on 2019-09-12T16:25:08 (imported from GitLab)
- bmortier changed due date to September 16, 2019
changed due date to September 16, 2019
By bmortier on 2019-09-12T16:25:11 (imported from GitLab)
- bmortier added fusiondirectory-core label
added fusiondirectory-core label
This is because of the ACL system, there is currently no ACL for
createTimestamp
normodifyTimestamp
.Potential solutions:
- Add ACLs for these fields (for all object types)
- For all unknown fields, consider read rights on all subcategories is needed, as is done for access to the LDAP dump tab
- For some fields (for instance
objectClass
,createTimestamp
andmodifyTimestamp
), consider them readable as soon as the object is visible (this how it’s done fordn
andbase
)
I’m not sure if creation/modification dates may be sensitive data in some cases or if they can always be visible. Option 2 may be done on top of option 1 or 3.
By Côme Chilliet on 2019-09-17T07:25:00 (imported from GitLab)
- bmortier added 10m of time spent at 2019-09-17
added 10m of time spent at 2019-09-17
By bmortier on 2019-09-17T07:28:58 (imported from GitLab)
- bmortier created merge request !672 to address this issue
created merge request !672 to address this issue
By Côme Chilliet on 2019-09-17T09:16:43 (imported from GitLab)
- bmortier mentioned in merge request !672
mentioned in merge request !672
By Côme Chilliet on 2019-09-17T09:16:43 (imported from GitLab)
- bmortier mentioned in issue #6028
mentioned in issue #6028
By Côme Chilliet on 2019-09-17T09:23:25 (imported from GitLab)
@jswaelens Please test this on as much management classes as possible, I only checked users.
ACLs for createTimestamp and modifyTimestamp are added if a class has an attribute named "base".
I did not add ACLs for creatorsName and modifiersName since with FD it will always contain the admin DN.
By Côme Chilliet on 2019-09-17T09:32:43 (imported from GitLab)
Edited by bmortier- bmortier added 2h of time spent at 2019-09-17
added 2h of time spent at 2019-09-17
By Côme Chilliet on 2019-09-17T09:32:32 (imported from GitLab)
- bmortier added To Be Tested label
added To Be Tested label
- bmortier assigned to @jswaelens and unassigned @MCMic
assigned to @jswaelens and unassigned @MCMic
By Côme Chilliet on 2019-09-17T09:32:32 (imported from GitLab)
I tested few case on demo-dev and it look good for most of them. It's juste supann entity and estabishement that didn't showed the create timestamp.
I tested the next objects department, users, groups/posix groups/roles, acl roles, sudo, dsa, applications, public forms, servers, workstations
By Jonathan Swaelens on 2019-09-18T13:10:58 (imported from GitLab)
- bmortier added 1h of time spent at 2019-09-18
added 1h of time spent at 2019-09-18
By Jonathan Swaelens on 2019-09-18T13:10:58 (imported from GitLab)
- bmortier removed To Be Tested label
removed To Be Tested label
- bmortier assigned to @MCMic and unassigned @jswaelens
assigned to @MCMic and unassigned @jswaelens
By Jonathan Swaelens on 2019-09-18T13:10:58 (imported from GitLab)