digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-09-20 01:07:18 +03:00
Code Issues Projects Releases Wiki Activity

Remove mentions of the token for package retrieval (#13330)

Browse Source 
It has been removed some time ago.

changelog_begin
changelog_end
This commit is contained in:
Stefano Baghino 2022-03-18 13:53:30 +01:00 committed by GitHub
parent 9b90a909cb
commit a4abb4ef9e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/source/json-api/index.rst
View File

@ -259,12 +259,13 @@ you can also use the ``--query-store-jdbc-config`` CLI flag (deprecated), an exa
Access Tokens
=============
The JSON API essentially performs two separate tasks:
Each request to the HTTP JSON API Service *must* come with an access token, regardless of whether the underlying ledger
requires it or not. This also includes development setups using an unsecured sandbox. The HTTP JSON API Service *does not*
hold on to the access token, which will only used to fulfill the request it came along with. The same token will be used
to issue the request to the Ledger API.
1. It talks to the Ledger API to get data it needs to operate, for this you need to *provide an access token* if your Ledger requires authorization. Learn more in the :doc:`/app-dev/authorization` docs.
2. It accepts requests from Parties and passes them on to the Ledger API, for this each party needs to provide an *access token with each request* it sends to the JSON API.
.. note:: By default, the Daml Sandbox does not does not require access tokens. However, you still need to provide a party-specific access token when submitting commands or queries as a party. The token will not be validated in this case but it will be decoded to extract information like the party submitting the command.
The HTTP JSON API Service does not validate the token but may need to decode it to extract information that can be used
to fill in request fields for party-specific request. How this happens depends partially on the token format you are using.
Party-specific Requests
-----------------------