You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.
Is there a way to expose a JEA endpoint as a web service, so that it could be used by an external system that knows how to make REST calls?
I already have a JEA endpoint that exposes a few custom cmdlets and it works through PS Remoting just fine. I've been asked to look into presenting those as a web service so that those same cmdlets could have been called by our ticketing system (which can make REST calls).
Thanks!
The text was updated successfully, but these errors were encountered:
Unfortunately, there are no plans to create a REST interface for JEA. JEA is a combination of PowerShell and WinRM features, so to create a REST interface we'd first need to create a full REST interface for PS Remoting over WinRM. Given the stateful nature of PowerShell, this is not a great fit or priority.
While it may not be useful in this particular instance, Windows Admin Center has shown that you can create a web interface for JEA using remote PowerShell from a web server.
Hi!
Is there a way to expose a JEA endpoint as a web service, so that it could be used by an external system that knows how to make REST calls?
I already have a JEA endpoint that exposes a few custom cmdlets and it works through PS Remoting just fine. I've been asked to look into presenting those as a web service so that those same cmdlets could have been called by our ticketing system (which can make REST calls).
Thanks!
The text was updated successfully, but these errors were encountered: