Connect fails with 404

[digitalfireinc]

It would seem that the auth URLS may have changed - I'm now getting 404 errors when trying to auth:

VERBOSE: Making token request to https://ca.ninjarmm.com:443/oauth/token
VERBOSE: Requested HTTP/1.1 POST with 218-byte payload
VERBOSE: Received HTTP/1.1 146-byte response of content type text/html
Invoke-WebRequest: 404 Not Found 404 Not Found nginx

Looks like the path should be /ws/oauth/token now.

[homotechsual]

Still working fine here using the standard path (which is the path in the docs as well!) Tested against eu. I can reach out to the API team to check if CA has changed for some reason.

[digitalfireinc]

The CA instance did update last night. Also, the docs I'm seeing (both old and new version) are showing the /ws/ in the path, more so in the testing spots. Looks like they didn't update the images though.

[homotechsual]

Ninja support have confirmed the issue. There is a temporary workaround and I think it might warrant a module release to fix - I'll see about doing that tomorrow if I can!

[homotechsual]

Ninja are saying it should be fixed now :-)

[digitalfireinc]

It is indeed - thanks Mikey for facilitating that!

[homotechsual]

I take no credit. All on Ninja!

[OstrichTyphoon]

Think this may have happened again! If I update the path to "/ws/oauth/token" all works fine, but otherwise I get "An error occurred. Sorry, the page you are looking for is currently unavailable. Please try again later. If you are the system administrator of this resource then you should check the error log for details. Faithfully yours, nginx."

[homotechsual]

It has - a fix has been merged already and I'm hoping to get a release out soon but adding the new 5.9 endpoints is taking time!

[digitalfireinc]

It would seem the 'fix' that Ninja did to the CA tenant previously is still holding after this update, as I'm still able to connect. Perhaps they did this to other tenants this time around?