Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

I'm curious about the Fosite decision to encode `token_type` as `bearer` rather than `Bearer`. I believe the responsible line of code is <https://github.com/ory/fosite/blob/3ec8db807b5ee7a9070f46304c9a183f2bba7c7b/handler/oauth2/helper.go#L33|here>

1. Is Ory strongly opinionated about this being `bearer` instead of `Bearer`? 
2. I know the spec indicates `token_type` here should be treated as case-insensitive, but the reality is that many libraries simply concatenate the `token_type` value into the `Authorization` header, resulting in an out-of-spec `Authorization: bearer foo` value. Would Ory be open to a PR to update this to `Bearer` to work better with these (badly behaving) libraries? 

I definitely don't think ory/fosite is in the wrong here; it's following the spec -- just curious if these types of PRs would be accepted, to help deal with poorly-behaving libraries.