`BasicAuth` extract error: invalid Header provided for correctly configured headers

[sikula]

/about output:

{
  "version": "v1.7.3",
  "uiVersion": "v0.9.18",
  "commit": "624aef0",
  "deploymentId": "01JN3J24J4D87B8TKMV4R75484",
  "updateAvailable": false,
  "latestVersion": "v1.7.3",
  "llmActive": false,
  "llmProvider": null,
  "oidcActive": false,
  "license": "AGPL-3.0-only",
  "mode": "Standalone",
  "staging": "/staging",
  "hotTier": "Disabled",
  "grpcPort": 8001,
  "store": {
    "type": "S3 bucket",
    "path": "http://minio:9000/newrali-local"
  },
  "analytics": {
    "clarityTag": null
  }
}

Description:

When forwarding logs from otel collector, Parseable logs failed with DEBUG actix_web_httpauth::extractors::basic: BasicAuth extract error: invalid Header provided even though the otel collector is correctly configured with the correct Authorization header, confirmed because a curl request with the exact same header successfully creates an event in Parseable

[nitisht]

Thanks for reporting @sikula we'll take a look shortly

[sikula]

Just for more context, I have an otel collector running with the following configuration

receivers:
  otlp:
    protocols:
      http:
        endpoint: "0.0.0.0:4318"


exporters:
  otlphttp/parseabletraces:
    endpoint: "http://localhost:4242"
    headers:
      Authorization: Basic cGFyc2VhZG1pbjpwYXJzZWFkbWlu
      X-P-Log-Source: otel-traces
      X-P-Stream: otel-traces
      Content-Type: application/json
    encoding: json
    tls:
      insecure: true

  debug:
    verbosity: detailed
    sampling_initial: 5
    sampling_thereafter: 200

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [otlphttp/parseabletraces, debug]

The traces are being picked up by the otel collector, and parseable does seem to see the request:

2025-02-27T16:19:52.132763Z  INFO actix_web::middleware::logger: 192.168.107.1 "POST /v1/traces HTTP/1.1" 200 0 "-" "OpenTelemetry Collector/0.120.1 (darwin/arm64)" 0.016495

But parseable doesn't show any results in the UI. Whenever performing some action in the UI the logs show the invalid Header error, so this might actually just be a different problem