-
Notifications
You must be signed in to change notification settings - Fork 904
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
Remove org.openbmc.* from REST server #2378
Comments
@ngorugan @bradbishop I'm thinking this can be a plug-in which runs on each request, checks if the request url consists of /org/openbmc, if so, fails with a 'not allowed'. |
https://gerrit.openbmc-project.xyz/7422 Remove org.openbmc.* from REST server |
This breaks the code update for non-UBIFS BMCs, a.k.s all OpenBMC machines except Witherspoon. |
We'll need to put this new code in it's own file, so it can easily be pulled in for just systems that want it. |
https://gerrit.openbmc-project.xyz/10209 Remove org.openbmc.* from REST server |
As per new changes openbmc/openbmc#2378 the /org/ and /xyz/ are no longer accessible. The URLs listed below are white-listed. { "urls": [ "/org/open_power/*", "/com/ibm/*", "/xyz/openbmc_project/*", "/enumerate", "/list", "/login", "/logout", "/subscribe", "/upload/image", "/download/dump/*" ] } Resolves #1423 Change-Id: I6d033dc4b53af06adb655c40cea6cd58270be8fa Signed-off-by: George Keishing <gkeishin@in.ibm.com>
cde:info SW407587 </cde:info>
The goal here is to put a filter on what the REST server allows users to read and write. Basically anything using the old org.openbmc would not be allowed in our out via REST.
The text was updated successfully, but these errors were encountered: