-
Notifications
You must be signed in to change notification settings - Fork 84
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
Security and Compliance PowerShell RPS Migration #59
Comments
It's now migrated on dev branch. It will be merged to main branch asap |
This enhacement was reopened. As far as I can see the rest of the CmdLets that requiring an active PowerShell PSSession were migrated to a REST-based commands. Monkey365 should migrate those CmdLets and to route commands to REST. |
Hi, I am unsure if this is related to this, but I can see below the warning and not results for Security and Compliance. Warning
Parameters:
Tested with this release:
OS: Windows11 - Windows365/CloudPC
thanks in advance, |
Hi @master-qwerty I believe is related to this issue and should be fixed in the next version.I'll leave this opened to better track it. Thanks |
Migration is now completed and RPS was migrated to REST based queries. |
Is your feature request related to a problem? Please describe.
Remote PowerShell (RPS) protocol is deprecated and will be decommissioned in the near future (October 2023). Monkey365 is still connecting to Security and Compliance through Remote PowerShell (RPS) and therefore should be migrated to REST API.
Describe the solution you'd like
Migrate all Security and Compliance related plugins and update Monkey365 codebase to use the new REST endpoints
Additional context
Deprecation of Remote PowerShell (RPS) Protocol in Security and Compliance PowerShell
The text was updated successfully, but these errors were encountered: