Default file/workunit access problems with new deployment
Environment
LDAP enabled security, new deployment
Description
When a file scope or workunit scope does not exist, the LDAP Security manager applies the "default" permissions which are those assigned to the parent OU (ou=Files, ou=Workunits).
A while back these permissions were changed to initialize to "Administrators Only", which meant a user could never access a file or workunits that were not scoped. The documentation clearly states that the user should be able to access these resources out of the box, so the creational atttibutes of these OUs should grant access to users
Conclusion
None
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
When a file scope or workunit scope does not exist, the LDAP Security manager applies the "default" permissions which are those assigned to the parent OU (ou=Files, ou=Workunits).
A while back these permissions were changed to initialize to "Administrators Only", which meant a user could never access a file or workunits that were not scoped. The documentation clearly states that the user should be able to access these resources out of the box, so the creational atttibutes of these OUs should grant access to users