Skip to content
New issue

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

External Command Permissions #25

Closed
box293 opened this issue Dec 6, 2017 · 3 comments
Closed

External Command Permissions #25

box293 opened this issue Dec 6, 2017 · 3 comments
Assignees
Milestone

Comments

@box293
Copy link
Contributor

box293 commented Dec 6, 2017

It would be useful if you could define granular permissions for the external commands. For example I want to allow a token to ACKNOWLEDGE_HOST_PROBLEM and ACKNOWLEDGE_SVC_PROBLEM however I don't want it to be able to DISABLE_HOST_CHECK, DISABLE_HOST_SVC_CHECKS, DISABLE_PASSIVE_HOST_CHECKS, DISABLE_PASSIVE_SVC_CHECKS.

I understand that connection to NRDP can be something other than a token, whatever authentication method used would have these permissions used.

@hedenface hedenface added this to the 1.5.0 milestone Dec 21, 2017
@hedenface hedenface self-assigned this Dec 21, 2017
@hedenface hedenface added the Bug label Dec 21, 2017
@hedenface
Copy link
Contributor

Fixed in f7c2764

@hedenface hedenface reopened this Dec 21, 2017
@hedenface
Copy link
Contributor

I had two issues open at once. That commit was actually the fix for #13.

@hedenface
Copy link
Contributor

Added in 0525b8d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants