question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Manage default ACLs

See original GitHub issue

Enhancement Request

Description

When new group is created this ACLs is applied by default:

 1084     @580     -H---------------     *     -m--    #0
 1085     @580     --N----D---------     *     u---    #0

And there is no way for override this behavior, even if you do this with one.group.allocate method through XML-RPC API.

Use case

I use groups for manage quotas first and foremost, so I have a lot of groups. But even more groups I have ACL rules, because when new group is created, two new ACLs was added.

For example: I don’t need Datastore and Network permisions by default that creates by default when group is created. I want to set access for selected datastores manually, by chmod permisions of resource. But for now, I need remove all default acl’s after group is created.

Interface Changes

I think there is can be some option in oned.conf file for disable or override default ACLs Another way add third optional parameter (type: boolean) to one.group.allocate method for disable new ACLs when group creating. In second case we also need additional key in CLI chekbox in Sunstone, when group is creating

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:2
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
rsmonterocommented, Jan 3, 2018

This seems to be already implemented as discussed here: https://forum.opennebula.org/t/overriding-default-acls/5468/4

0reactions
kvapscommented, Mar 6, 2019

This issue can be closed, now default permissions can be set via oned.conf:

DEFAULT_VDC_HOST_ACL      = ""
DEFAULT_VDC_VNET_ACL      = ""
DEFAULT_VDC_DATASTORE_ACL = ""
DEFAULT_VDC_CLUSTER_HOST_ACL      = ""
DEFAULT_VDC_CLUSTER_NET_ACL       = ""
DEFAULT_VDC_CLUSTER_DATASTORE_ACL = ""
Read more comments on GitHub >

github_iconTop Results From Across the Web

8.3. Setting Default ACLs
To set a default ACL, add d: before the rule and specify a directory instead of a file name. For example, to set...
Read more >
20.3. Setting Default ACLs Red Hat Enterprise Linux 6
To set a default ACL, add d: before the rule and specify a directory instead of a file name. Example 20.3. Setting default...
Read more >
Working with default ACLs - IBM
To facilitate management of ACLs, you can define a default ACL in a directory; it will then be automatically inherited by an object....
Read more >
Secure Files/Directories using ACLs (Access Control Lists) in ...
To set the default ACLs for a specific file or directory, use the 'setfacl' command. In the example below, the setfacl command will...
Read more >
Using Access Control Lists (ACLs) (System Administration Guide
Specifies the list of one or more ACL entries to set for specific users and groups on the file or directory. You can...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found