Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

allow secure connection from JSON API to ledger #5555

Merged
merged 9 commits into from
Apr 16, 2020
Merged

allow secure connection from JSON API to ledger #5555

merged 9 commits into from
Apr 16, 2020

Commits on Apr 14, 2020

  1. factor TlsConfiguration parser from extractor

    @S11001001
    S11001001 committed Apr 14, 2020
    Configuration menu
    Copy the full SHA
    716f138 View commit details
    Browse the repository at this point in the history

  2. move TlsConfigurationParser to new library

    @S11001001
    S11001001 committed Apr 14, 2020
    Configuration menu
    Copy the full SHA
    ba8653c View commit details
    Browse the repository at this point in the history

  3. link extractor to ledger-service/cli-opts properly

    @S11001001
    S11001001 committed Apr 14, 2020
    Configuration menu
    Copy the full SHA
    573e276 View commit details
    Browse the repository at this point in the history

  4. use TlsConfigurationCli in http-json, pass SslContext to ledger-client

    @S11001001
    S11001001 committed Apr 14, 2020
    Configuration menu
    Copy the full SHA
    7eede34 View commit details
    Browse the repository at this point in the history

Commits on Apr 15, 2020

  1. test TLS options as used in http-json 

    - the TLS config code is shared with extractor, where it is more fully
  tested; we just do a sanity check here
    @S11001001
    S11001001 committed Apr 15, 2020
    Configuration menu
    Copy the full SHA
    e4b9cae View commit details
    Browse the repository at this point in the history

  2. doc TLS options for http-json 

    CHANGELOG_BEGIN
- [JSON API] New ``--pem``, ``--crt``, ``--cacrt``, and ``--tls`` options
  for securing the connection between JSON API server and ledger.
  See `issue #2540 <https://github.com/digital-asset/daml/issues/2540>`__.
CHANGELOG_END
    @S11001001
    S11001001 committed Apr 15, 2020
    Configuration menu
    Copy the full SHA
    9129e6a View commit details
    Browse the repository at this point in the history

  3. Merge commit 'd83387a64d47fcbf9bd2450c8c2efa78a8c4e846' into 2540-jso… 

    …n-api-crypt-grpc
    @S11001001
    S11001001 committed Apr 15, 2020
    Configuration menu
    Copy the full SHA
    edee3cc View commit details
    Browse the repository at this point in the history

Commits on Apr 16, 2020

  1. Merge commit '02eadf68c8081a99b8ceb95447044e0218b7d16a' into 2540-jso… 

    …n-api-crypt-grpc
    @S11001001
    S11001001 committed Apr 16, 2020
    Configuration menu
    Copy the full SHA
    e799e46 View commit details
    Browse the repository at this point in the history

  2. TLS off in daml-script JSON API test

    @S11001001
    S11001001 committed Apr 16, 2020
    Configuration menu
    Copy the full SHA
    31a1b17 View commit details
    Browse the repository at this point in the history