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

feat: allow for ExApps to call Admin endpoints marked with specific attribute #46539

Closed
wants to merge 3 commits into from

Conversation

bigcat88
Copy link
Member

@bigcat88 bigcat88 commented Jul 15, 2024

Summary

We need this for the Workflow Engine Project, and not only.

The option of duplicating ednpoints where they do not require the admin flag to be set seems to us not quite the right solution; sometimes for ExApps you still need to check whether the user is an administrator or not.

  1. If you need to check the user for ExApp and it works in the user’s context, it sets the userId and everything works as it did.
  2. Only if the request comes from ExApp and the user is not set in the session, then the check for the attributes "AuthorizedAdminSetting" and "SubAdminRequired" is skipped.

Checklist

@julien-nc
Copy link
Member

@nickvergessen What do you think about that?

@nickvergessen
Copy link
Member

Will have a look and answer tomorrow.

Copy link
Member

@nickvergessen nickvergessen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this opens a wide angle on our APIs, we should make sure that logging (and admin audit logging) is also aware of $this->userSession->getSession()->get('app_api') and properly logs that an action was performed "on behalf of a user" and not "by a user".

But be very careful in the logging so it never fails (catch throwable, etc.) as otherwise logging breaks completely.

@nickvergessen
Copy link
Member

Additionally this would allow a malicious admin to escape AuthorizedAdminSetting ?

…ttribute

Signed-off-by: Alexander Piskun <bigcat88@icloud.com>
@bigcat88 bigcat88 force-pushed the feat/AppApiAdminAccessWithoutUser-attribute branch from defc4e0 to 3aec0da Compare July 18, 2024 08:17
@bigcat88
Copy link
Member Author

Additionally this would allow a malicious admin to escape AuthorizedAdminSetting ?

If I correctly understood the situation you describe, then the answer is probably “no”:
to do this, the administrator must have access to the infrastructure to obtain the ExApp key.

Since this opens a wide angle on our APIs, we should make sure that logging (and admin audit logging) is also aware of $this->userSession->getSession()->get('app_api') and properly logs that an action was performed "on behalf of a user" and not "by a user".

But be very careful in the logging so it never fails (catch throwable, etc.) as otherwise logging breaks completely.

should this be done in a separate PR for cleanliness?

@bigcat88 bigcat88 marked this pull request as ready for review July 18, 2024 09:33
@bigcat88 bigcat88 added the 3. to review Waiting for reviews label Jul 18, 2024
@nickvergessen
Copy link
Member

If I correctly understood the situation you describe, then the answer is probably “no”:
to do this, the administrator must have access to the infrastructure to obtain the ExApp key.

Might be a "no brainer", but I meant if they can install exapps they can now also perform admin actions on the server (on any level), by writing their own exapp and enabling it.
But mostlikely they could also do a normal php app then

@nickvergessen
Copy link
Member

should this be done in a separate PR for cleanliness?

If you can do it in a separate PR before beta1 next week?

@bigcat88
Copy link
Member Author

I will re-create this PR as I messed it with merging commits from master branch.

@bigcat88 bigcat88 closed this Jul 18, 2024
@bigcat88 bigcat88 deleted the feat/AppApiAdminAccessWithoutUser-attribute branch July 18, 2024 12:02
bigcat88 added a commit to nextcloud/app_api that referenced this pull request Aug 15, 2024
1. Logs are written to a separate file
2. Log level - Warning
3. Only for those requests where "user" is set

Reference:
nextcloud/server#46539 (review)

this is how logs look like:

```json
{"reqId":"t9ThOI2CheVn6sDUsUKO","level":2,"time":"2024-08-13T10:08:42+00:00","remoteAddr":"192.168.65.1","user":"admin","app":"nc_py_api","method":"GET","url":"/ocs/v1.php/cloud/capabilities?format=json","message":"impersonation request","userAgent":"python-httpx/0.25.2","version":"30.0.0.7","data":{"app":"nc_py_api"}}
{"reqId":"tVtHIEwQ5YKhbWUFTmKF","level":2,"time":"2024-08-13T10:08:42+00:00","remoteAddr":"192.168.65.1","user":"admin","app":"nc_py_api","method":"PROPFIND","url":"/remote.php/dav/files/admin","message":"impersonation request","userAgent":"python-httpx/0.25.2","version":"30.0.0.7","data":{"app":"nc_py_api"}}
```

Signed-off-by: Alexander Piskun <bigcat88@icloud.com>
Copy link
Contributor

github-actions bot commented Nov 7, 2024

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

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

Successfully merging this pull request may close these issues.

3 participants