Closed mrabus closed 2 years ago
It seems to be a webservice (IIS? - redirected?) that is intervening .. .
Could it be some kind of firewall that prevents some kind of PATCH method? Or the command is blocked on iis? Or anything that's in between?
It does NOT seem to be a BC problem - as it's not a BC error message.. . I'd look into the infrastructure.
ALOps prints the method and the url - you should be able to test that in e.g. postman.. .
Were you able to test it?
@mrabus ?
I'm closing this issue. If you feel the need to reopen it, please feel free to do so.
I had the same issue and the problem disappeared when the customers IT-guys loosen up the firewall/redirection rules
Describe the bug I try to publish a single app using the ALOps Extension API task. This fails with the following error:
the used yaml
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior Best case, the app is published without issues. Otherwise any hint what is going wrong would be awesome.
Additional context I tried to check some issues. The automation API is reachable from the internet, otherwise the queries for the companies and the installed apps would fail, too. The user has SUPER, D365 AUTOMATION and Exten. MGT. - ADMIN permissions, so that should be okay.
The installation of the external deployer is okay as well. I was able to publish the app through the page 2507 before without issues.
Any help would be much appreciated