QTest 9.2 REST API Authorization Header Shift from Bearer to QTestToken Breaks Legacy Integrations

Goal: Verify whether a QTest 9.2 server returns a WWW‑Authenticate challenge that indicates the expected Authorization scheme when a client sends a legacy Bearer token, allowing integrations to detect the required header format automatically.

Constraints: The upgrade from 9.1 to 9.2 changed the header from Bearer to QTestToken with no deprecation warning or response body detail; legacy requests receive a 401 Unauthorized but may lack any challenge header, making silent failures possible. Testing must be done in a staging environment to avoid production impact.

Specific questions: Does the 401 response include a WWW‑Authenticate header with the scheme QTestToken? If not, is there any alternative endpoint or response field that advertises supported authentication schemes? What minimal change can be made to client‑side middleware to detect the required scheme without relying on trial‑and‑error requests?