From 2c7a1b1fb2b0ed3aba5a36795550e1cdc76786ac Mon Sep 17 00:00:00 2001 From: Sebastian Schildt Date: Mon, 18 Sep 2023 17:30:41 +0200 Subject: [PATCH] Address review findings Signed-off-by: Sebastian Schildt --- kuksa-client/README.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/kuksa-client/README.md b/kuksa-client/README.md index a30bfceb..9c9da06a 100644 --- a/kuksa-client/README.md +++ b/kuksa-client/README.md @@ -27,12 +27,7 @@ After you have installed the kuksa-client package via pip you can run the test c $ kuksa-client ``` -With default CLI arguments, the client will try to connect to a local databroker, e.g. a server supporting the `kuksa.val.v1` protocol.. -If you wish to connect to a VISS server e.g. `kuksa-val-server`, you should instead run: - -```console -$ kuksa-client ws://127.0.0.1:8090 -``` +With default CLI arguments, the client will try to connect to a local Databroker, e.g. a server supporting the `kuksa.val.v1` protocol without using TLS. If everything works as expected and the server can be contacted you will get an output similar to below. @@ -55,7 +50,7 @@ Welcome to Kuksa Client version Default tokens directory: /some/path/kuksa_certificates/jwt -Connecting to VSS server at 127.0.0.1 port 55556 using KUKSA GRPC protocol. +Connecting to VSS server at 127.0.0.1 port 55555 using KUKSA GRPC protocol. TLS will not be used. INFO 2023-09-15 18:48:13,415 kuksa_client.grpc No Root CA present, it will not be posible to use a secure connection! INFO 2023-09-15 18:48:13,415 kuksa_client.grpc.aio Establishing insecure channel @@ -63,6 +58,12 @@ gRPC channel connected. Test Client> ``` +If you wish to connect to a VISS server e.g. `kuksa-val-server` (not using TLS), you should instead run: + +```console +$ kuksa-client ws://127.0.0.1:8090 +``` + If the connected KUKSA Server or KUKSA Databroker require authorization the next step is to authorize. KUKSA Server and KUKSA Databroker use different token formats.