Open aHenryJard opened 2 weeks ago
OpenCTI Taxii server return HTTP 200 OK for bad credentials instead of HTTP 403.
The consequence is that using OpenCTI as taxii client with another OpenCTI => there is no error, so no error log to understand the issue.
Steps to create the smallest reproducible scenario:
Expect to have an HTTP error 403 forbidden
HTTP 200 OK and OpenCTI login page as HTML in the response body
Please check also other Taxii server error (like 500).
Not sure why but I think the behavior has changed, it's now sending a HTTP 500. But still not the right HTTP code, should be just forbidden.
Description
OpenCTI Taxii server return HTTP 200 OK for bad credentials instead of HTTP 403.
The consequence is that using OpenCTI as taxii client with another OpenCTI => there is no error, so no error log to understand the issue.
Environment
Reproducible Steps
Steps to create the smallest reproducible scenario:
Expected Output
Expect to have an HTTP error 403 forbidden
Actual Output
HTTP 200 OK and OpenCTI login page as HTML in the response body
Additional information
Please check also other Taxii server error (like 500).
Screenshots (optional)