Dynatrace problem notification to execute a script on a remote node

[Erick Chwallah]

I am facing a challenge running a test notification to execute a script on a remote node.

My rundeck instance is self-hosted on Azure cloud

I am getting the error on Dynatrace even though I have created the API token as admin in Rundeck and referenced the correct Job UUID.

Any help to resolve this?

  {"error":true,"apiversion":52,"errorCode":"unauthorized","message":"(unauthenticated) is not authorized for: /api/52/job/8f7e9429-c480-4da1-8398-16f333dc5951/run"}

My webhook url is   

http://<your-rundeck-server>/api/52/job/8f7e9429-c480-4da1-8398-16f333dc5951/run

I have placed the token under additional headers in Dynatrace with 

• keyname Authorization

• Value Bearer <token value created in rundeck>

[rac...@rundeck.com]

Hi,

Did you test that call using CURL to discard any Rundeck-side problem? Take a look at this.

I’m not a Dynatrace expert but checking the docs, you can define headers in the webhook calls. Try adding the X-Rundeck-Auth-Token header with the Rundeck token, just like the first link example.

Regards.

​

[Erick Chwallah]

Hello I added the Additional headers as mentioned in Dynatrace and the same curl command from a powershell or command prompt still throws the same error of unauthorised.

My curl command looks like this

curl -X POST http://20.65.153.222/api/52/job/8f7e9429-c480-4da1-8398-16f333dc5951/run -H "Authorization: Bearer <Rundeck Token>"

so it fails with the same error outside of Dynatrace hence ruling out Dynatrace.

What could be missing here???

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rundeck-discuss/3b823e93-ce41-44fc-8de3-3a0322d4bc9fn%40googlegroups.com.

--

Chwallah, Erick James

Bsc. Computer Science , Msc. Bioinformatics and Molecular Biology,  CISSP-ISC2

Systems Developer,Information Systems Security Analyst, Digital Forensics Expert
    

[Erick Chwallah]

Thanks this finally worked after I referenced the API reference documentation.

The header should be X-Rundeck-Auth-Token and value as the Token string.

Thanks for the insight

[rac...@rundeck.com]

Great! Happy to help!