saltstack / saltstack/salt

[FEATURE REQUEST] Document and test support for @wheel, @runner and @jobs syntax in publisher_acl

Open
#61,769 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

doc-ex-missing doc-request documentation security severity-medium Tests time-estimate-sprint
Dominant language
Python
Stars
15.7k
Forks
5.6k
Avg merge
2d 44m
Merged PRs (30d)
80

Description

Opened as a task for the Security WG

Is your feature request related to a problem? Please describe.

As part of the work to implement SEP19 we need to be able to run the salt-master process as a non-root user that is also a member of a shared group that will be used to allow users to run the salt cli tools.

This will require the use of the Publisher ACL system to control access to salt functionality for non-root users using the salt cli commands.

It's not clear from the Publisher ACL docs if the ACL syntax supports the @wheel, @runner and @jobs syntax that the eauth ACLs do. The docs just say that "This configuration is much like the external_auth configuration"

Describe the solution you'd like

Review code and test to see if the Publisher ACL support the syntax.

Update the docs

Additional context

SEP19

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 with the Publisher ACL documentation and the linked eauth ACL documentation, then inspect the Publisher ACL implementation and its existing tests for support of @wheel, @runner, and @jobs. Done means the supported syntax is verified by tests and the Publisher ACL documentation clearly describes the result.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authorization, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.