401 Unauthorized error in Jaeger client integration

Goal

Develop a test harness for a Jaeger client that can be run in CI or local environments without using real production credentials.

Constraints and Uncertainty

• The Jaeger client library expects an authentication token or basic auth header when sending spans to a secured collector.
• Using production credentials in tests is forbidden by policy, yet the collector endpoint still requires authentication.
• It is unclear whether Jaeger provides a built‑in mechanism to bypass authentication or to supply a mock authentication provider for testing.

Specific Questions

1. Can the Jaeger client be configured to use a mock or stub authentication provider so that it accepts spans without real credentials?
2. What configuration flags or environment variables enable the Jaeger collector to accept unauthenticated requests during integration tests?
3. Is there a recommended pattern for using an in‑memory reporter or local collector that eliminates the need for authentication entirely?