You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
For simplicity. Create a user and create a simple publisher_acl restriction (see below) and run a command not in the publisher ACL. In a previous salt version 3004 for us. The example below would properly give us an authentication issue if we did anything not defined in the publisher_acl. So if you ran
salt '*' test.ping
Authorization error occurred. (the result we would expect)
And
salt '*' pillar.items
(and the display would be the pillar values as we would expect).
For testing use a simple setup:
Add proper user.
publisher_acl:
USER-NAME:
- pillar.items
Run a (with user in publisher_acl
salt '*' test.ping
Expected result:
Authorization error occurred.
Actual result:
Minions ping back.
Setup
create a user & set the publisher_acl to limit the user to be able to run a few salt commands
publisher_acl:
USER-NAME:
- pillar.items
switch to the user created and run a
salt '*' test.ping
Then run a
salt '*' pillar.items
on-prem machine
VM (Virtualbox, KVM, etc. please specify)
KVM
VM running on a cloud service, please be explicit and add details
container (Kubernetes, Docker, containerd, etc. please specify)
or a combination, please be explicit
jails if it is FreeBSD
classic packaging
onedir packaging
used bootstrap to install
Steps to Reproduce the behavior
(Include debug logs if possible and relevant)
Expected behavior
When a command is run that is allowed it should run. When a command is not specified to be allowed it should be:
Authorization error occurred.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
Salt Version:
Salt: 3006.6Python Version:
Python: 3.10.13 (main, Nov 15 2023, 04:34:27) [GCC 11.2.0]Dependency Versions:
cffi: 1.16.0cherrypy: unknowndateutil: 2.8.1docker-py: Not Installedgitdb: 4.0.11gitpython: 3.1.40Jinja2: 3.1.3libgit2: Not Installedlooseversion: 1.0.2M2Crypto: Not InstalledMako: Not Installedmsgpack: 1.0.2msgpack-pure: Not Installedmysql-python: Not Installedpackaging: 22.0pycparser: 2.21pycrypto: Not Installedpycryptodome: 3.19.1pygit2: Not Installedpython-gnupg: 0.4.8PyYAML: 6.0.1PyZMQ: 23.2.0relenv: 0.14.2smmap: 5.0.1timelib: 0.2.4Tornado: 4.5.3ZMQ: 4.3.4System Versions:
dist: rhel 9.3 Plowlocale: utf-8machine: x86_64release: 5.14.0-362.18.1.el9_3.x86_64system: Linuxversion: Red Hat Enterprise Linux 9.3 Plow
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Description
For simplicity. Create a user and create a simple publisher_acl restriction (see below) and run a command not in the publisher ACL. In a previous salt version 3004 for us. The example below would properly give us an authentication issue if we did anything not defined in the publisher_acl. So if you ran
And
(and the display would be the pillar values as we would expect).
For testing use a simple setup:
Add proper user.
Run a (with user in publisher_acl
Expected result:
Actual result:
Minions ping back.
Setup
create a user & set the publisher_acl to limit the user to be able to run a few salt commands
switch to the user created and run a
Then run a
Steps to Reproduce the behavior
(Include debug logs if possible and relevant)
Expected behavior
When a command is run that is allowed it should run. When a command is not specified to be allowed it should be:
Screenshots
If applicable, add screenshots to help explain your problem.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: