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

API: support "asUser" for listing nodes #2270

Closed
rophy opened this issue Jan 10, 2017 · 1 comment
Closed

API: support "asUser" for listing nodes #2270

rophy opened this issue Jan 10, 2017 · 1 comment

Comments

@rophy
Copy link
Contributor

rophy commented Jan 10, 2017

Currently API only supports "asUser" for running jobs and running ad-hoc commands.

If "asUser" for listing nodes is supported, then #2255 will be possible through remote option.

@rophy rophy changed the title API: support "runAs" for listing nodes API: support "asUser" for listing nodes Jan 10, 2017
@gschueler
Copy link
Member

asUser does not change authorization, only records a different username for adhoc/job executions. IMO asUser for listing nodes would not achieve what you want. for #2255 I think we should add that internally so it wouldn't have to use remote url option anyway.

Additionally, the asUser for jobs/adhoc is probably going to be deprecated. We now have user and service API tokens, which allows another username to be used with a token. I think we should improve recording of the "user" who performs the action (adhoc/job run or kill) to include the user "name" as well as any auth token origin name (i.e. who created the token, or the token ID), this will accurately record the authorization info, as well as the user for whom the action was performed "on behalf of"

I am going to close this, but if you have another reason for this feature, please reopen. thanks.

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