mirror of
https://github.com/digital-asset/daml.git
synced 2024-11-10 10:46:11 +03:00
0f4fb9a8f5
* sandbox: Add a database test for storing and retrieving parties. * sandbox: Add database queries for selecting one or many parties. * ledger-api-test-tool: Add a test for `ListKnownParties`. * sandbox: Add an endpoint to retrieve a single party's details. CHANGELOG_BEGIN - [Ledger API] Added an endpoint to retrieve a single party's details at ``com.digitalasset.ledger.api.v1.admin.PartyManagementService.GetParty``. Please consult the ledger API reference documentation for more information. CHANGELOG_END * sandbox: Add an endpoint to retrieve a multiple parties' details. CHANGELOG_BEGIN - [Ledger API] Added an endpoint to retrieve multiple parties's details at ``com.digitalasset.ledger.api.v1.admin.PartyManagementService.GetParties``. Please consult the ledger API reference documentation for more information. CHANGELOG_END * sandbox: Getting a single party is a special case of multiple parties. So let's use that code path and stop duplicating work. * sandbox: Remove `GetParty`, as it's subsumed by `GetParties`. "Subsumed" is a great word. |
||
---|---|---|
.. | ||
src | ||
BUILD.bazel | ||
README.md |
Ledger API authorization
General authorization in gRPC
An Interceptor
reads HTTP headers, and stores relevant information (e.g., claims) in a Context
.
GRPC services read the stored data from the Context
in order to validate the requests.
Authorization in the ledger API
The AuthService
defines an interface for decoding HTTP headers into Claims
.
The ledger API server takes an AuthService
implementation as an argument.
The ledger API server uses a call interceptor and the given AuthService
implementation to to store decoded Claims
in the gRPC Context
.
All ledger API services use the Claims
to validate their requests.