We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12259
Created by aledermueller on 2016-07-29 14:47:01 +00:00
Assignee: mfriedrich Status: Resolved (closed on 2016-07-29 15:01:13 +00:00) Target Version: 2.5.0 Last Update: 2016-08-22 11:58:30 +00:00 (in Redmine)
Icinga Version: 2.4.10 Backport?: Not yet backported Include in Changelog: 1
In the permissions table in 11.2.5 [1] the permission for status query should be 'status/query' and not 'status/query/'
[1] http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/icinga2-api
Regards, Achim
Changesets
2016-07-29 15:00:36 +00:00 by mfriedrich 19fb71e
Docs: Fix API permissions for status/query fixes #12259
The text was updated successfully, but these errors were encountered:
Updated by mfriedrich on 2016-07-29 15:01:04 +00:00
Thanks fixed.
Sorry, something went wrong.
Updated by mfriedrich on 2016-07-29 15:01:13 +00:00
Applied in changeset 19fb71e.
Updated by gbeutner on 2016-08-22 11:58:30 +00:00
No branches or pull requests
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12259
Created by aledermueller on 2016-07-29 14:47:01 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-07-29 15:01:13 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-22 11:58:30 +00:00 (in Redmine)
In the permissions table in 11.2.5 [1] the permission for status query should be 'status/query' and not 'status/query/'
[1] http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/icinga2-api
Regards,
Achim
Changesets
2016-07-29 15:00:36 +00:00 by mfriedrich 19fb71e
The text was updated successfully, but these errors were encountered: