Set the Bearer prefix in bindings.

[gerolf-da]

This means it must be removed in the token files.

CHANGELOG_BEGIN
[Extractor]: The Bearer prefix must be removed from the token file.
[Navigator]: The Bearer prefix must be removed from the token file.
CHANGELOG_END

Pull Request Checklist

• Read and understand the contribution guidelines
• Include appropriate tests
• Set a descriptive title and thorough description
• Add a reference to the issue this PR will solve, if appropriate
• Include changelog additions in one or more commit message bodies between the CHANGELOG_BEGIN and CHANGELOG_END tags
• Normal production system change, include purpose of change in description

NOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with /AzurePipelines run to
trigger the build.

[cocreature]

I’m a bit confused, I would have expected that we enforce this on the server side as well. Without doing this, this just limits the ledgers we can interact with.

Changelog is missing DAML Script,DAML Repl and the ledger bindings and I expect that there are also some docs that mention this (at the very least the docs for DAML Script over the JSON API has a caveat that it does not expect the Bearer prefix in the token file which is now redundant).

[gerolf-da]

@cocreature: I'm making a few more changes at the moment. I'm thinking of dropping the Bearer prefix altogether for the gRPC Ledger API. Might still make sense to keep it in the JSON API, as there the user needs to explicitly set http headers, whereas with gRPC it's just arbitrary metadata.

[cocreature]

Looks great ,thanks a lot! And sorry for the confusion.

[gerolf-da]

No no, thanks for asking the right questions, @cocreature!