This is my perspective to the current situation:
WAC includes a gateway service with translates REST API calls at northbound to powershell or WMI calls at the southbound interface.
But it seems to me, that the REST API service at he gateway is only reachable from WAC, not from the outside of WAC.
This is my feature request:
As REST API is the door opener for automation, it will be nice if Microsoft will support REST API for the automation of local environments and of course the necessary documentation for that.
This are my alternative thoughts:
using tools which provides the necessary REST API interface ( powerdns, kea, infoblox, aso... )
what else:
openid support will also be welcome to setup an environment with keycloak dealing with jwt for authentiction and authorization
comnam90
commented
2 years ago
This is my perspective to the current situation: WAC includes a gateway service with translates REST API calls at northbound to powershell or WMI calls at the southbound interface. But it seems to me, that the REST API service at he gateway is only reachable from WAC, not from the outside of WAC.
This is my feature request: As REST API is the door opener for automation, it will be nice if Microsoft will support REST API for the automation of local environments and of course the necessary documentation for that.
This are my alternative thoughts: using tools which provides the necessary REST API interface ( powerdns, kea, infoblox, aso... )
what else: openid support will also be welcome to setup an environment with keycloak dealing with jwt for authentiction and authorization