chef / chef/chef-server

can't fetch acl info without admins membership

Open
#739 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect: Testing Component: opscode-erchef Status: To be prioritized Triage: Confirmed Triage: Try Reproducing Type: Bug
Dominant language
Erlang
Stars
303
Forks
211
Avg merge
1d 8h
Merged PRs (30d)
5

Description

hi,

I was trying to fetch acl data for a node (via GETing /nodes/$node/_acl) and I'm receiving HTTP 403 with body of {"error":["missing read permission"]}
https://github.com/chef/chef-server/blob/master/src/oc_erchef/doc/API/acl.md#get-_acl-api
says that "The authorization service manages the permissions for who can read an ACL; at this time if you have any of CRUDG on the object you can read its ACL."
The acl for the given node allows create, read and update for the users groups (which my user is member of) so I think I should be allowed to fetch the acl data.
I can also confirm that I can fetch the acl information with another user which is member of the admins group.
Could you please clarify if this is a bug or a documentation problem (see the above statement and also https://docs.chef.io/api_chef_server.html lacks documentation on the /nodes/node/_acl endpoint).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the authorization behavior of GET /nodes/$node/_acl with the permissions described in src/oc_erchef/doc/API/acl.md and the Chef Server API documentation. Reproduce the 403 with a non-admin user who has CRUDG access, then compare it with the admin response. Done means the documented behavior and endpoint behavior agree, with an appropriate test or documentation update.

Written by the indexing model from the issue text.

Assessment

Tech stack
erlang
Domain
api, authorization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.