Authentication support in WHIP client

[birme]

WHIP endpoints and resources MAY require the HTTP request to be authenticated using an HTTP Authorization header with a Bearer token as specified in [RFC6750] section 2.1. WHIP clients MUST implemenent this authentication and authorization mechanism and send the HTTP Authorization header in all HTTP request sent to either the WHIP endpoint or resource.

https://www.ietf.org/archive/id/draft-ietf-wish-whip-01.html#section-4.5