-
Bug
-
Resolution: Unresolved
-
Low
-
Minor
Issue Summary
The new incoming webhook trigger returns 200 ok regardless of the secret value. This makes it harder to debug in case of actual failure.
Steps to Reproduce
- Open POSTMAN and create a new POST request.
- Enter the webhook URL in the URL field.
- Add a header with the name X-Automation-Webhook-Token and don't set the secret token or set a wrong token.
- Send the request and observe the response code.
Expected Results
An error code is expected indicating that the secret is missing or invalid.
Actual Results
A 200 response code is returned.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[AUTO-1720] The new Incoming webhook trigger returns 200 ok regardless of the secret token value
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Description |
Original:
h3. Issue Summary
The new incoming webhook trigger returns 200 ok regardless of the secret value. h3. Steps to Reproduce # Open POSTMAN and create a new POST request. # Enter the webhook URL in the URL field. # Add a header with the name X-Automation-Webhook-Token and don't set the secret token or set a wrong token. # Send the request and observe the response code. h3. Expected Results An error code is expected indicating that the secret is missing or invalid. h3. Actual Results A 200 response code is returned. !bug.png|thumbnail! !bugwrongvalue.png|thumbnail! h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
The new incoming webhook trigger returns 200 ok regardless of the secret value. This makes it harder to debug in case of actual failure. h3. Steps to Reproduce # Open POSTMAN and create a new POST request. # Enter the webhook URL in the URL field. # Add a header with the name X-Automation-Webhook-Token and don't set the secret token or set a wrong token. # Send the request and observe the response code. h3. Expected Results An error code is expected indicating that the secret is missing or invalid. h3. Actual Results A 200 response code is returned. !bug.png|thumbnail! !bugwrongvalue.png|thumbnail! h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Description |
Original:
h3. Issue Summary
The new incoming webhook trigger returns 200 ok regardless of the secret value. h3. Steps to Reproduce # Open POSTMAN and create a new POST request. # Enter the webhook URL in the URL field. # Add a header with the name X-Automation-Webhook-Token and don't set the secret token or set a wrong token. # Send the request and observe the response code. h3. Expected Results An error code is expected indicating that the secret is missing or invalid. h3. Actual Results A 200 response code is returned. !bug.png|thumbnail! h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
The new incoming webhook trigger returns 200 ok regardless of the secret value. h3. Steps to Reproduce # Open POSTMAN and create a new POST request. # Enter the webhook URL in the URL field. # Add a header with the name X-Automation-Webhook-Token and don't set the secret token or set a wrong token. # Send the request and observe the response code. h3. Expected Results An error code is expected indicating that the secret is missing or invalid. h3. Actual Results A 200 response code is returned. !bug.png|thumbnail! !bugwrongvalue.png|thumbnail! h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Attachment | New: bugwrongvalue.png [ 487485 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 993676 ] |
| Description |
Original:
h3. Issue Summary
The new incoming webhook trigger returns 200 ok regardless of the secret value. h3. Steps to Reproduce # Open POSTMAN and create a new POST request. # Enter the webhook URL in the URL field. # Add a header with the name X-Automation-Webhook-Token and don't set the secret token or set a wrong token. # Send the request and observe the response code. h3. Expected Results An error code is expected indicating that the secret is missing or invalid. h3. Actual Results A 200 response code is returned. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
The new incoming webhook trigger returns 200 ok regardless of the secret value. h3. Steps to Reproduce # Open POSTMAN and create a new POST request. # Enter the webhook URL in the URL field. # Add a header with the name X-Automation-Webhook-Token and don't set the secret token or set a wrong token. # Send the request and observe the response code. h3. Expected Results An error code is expected indicating that the secret is missing or invalid. h3. Actual Results A 200 response code is returned. !bug.png|thumbnail! h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Attachment | New: bug.png [ 487484 ] |
| Summary | Original: The new Incoming webhook trigger retrurn 200 ok regardless of the secret token value | New: The new Incoming webhook trigger returns 200 ok regardless of the secret token value |
| Labels | New: jsw-s13 |