Skip to content

Commit

Permalink
Final migration steps
Browse files Browse the repository at this point in the history
  • Loading branch information
erikbosch committed Dec 15, 2023
1 parent 321ae9a commit 6f07ed1
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 7 deletions.
3 changes: 0 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,6 @@
# KUKSA CAN Provider
![KUKSA Logo](./doc/img/logo.png)


**Note: Migration in progress! Please do not use yet!**

This is a DBC CAN provider for the
[KUKSA.val](https://raw.githubusercontent.com/eclipse-kuksa/kuksa-can-provider/main/doc/img/logo.png) Server and Databroker.
For [KUKSA Server](https://github.com/boschglobal/kuksa.val/tree/master/kuksa-val-server)
Expand Down
14 changes: 10 additions & 4 deletions config/dbc_feeder.ini
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,11 @@ tls = False

# TLS-related settings
# Path to root CA, needed if using TLS
root_ca_path=../../kuksa.val/kuksa_certificates/CA.pem
# The example below works if you have cloned kuksa.val in parallel to kuksa-can-provider
# root_ca_path=../kuksa.val/kuksa_certificates/CA.pem
# The example below works if you have cloned kuksa-coomon in parallel to kuksa-can-provider
# root_ca_path=../kuksa-common/tls/CA.pem

# Server name, typically only needed if accessing server by IP address like 127.0.0.1
# and typically only if connection to KUKSA.val Databroker
# If using KUKSA.val example certificates the names "Server" or "localhost" can be used.
Expand All @@ -45,12 +49,14 @@ root_ca_path=../../kuksa.val/kuksa_certificates/CA.pem
# Default behavior differ between servers
# For KUKSA.val Databroker the KUKSA.val default token not included in packages and containers
# If you run your Databroker so it require authentication you must specify token
# The example below works if you have cloned kuksa.val in parallel to kuksa.val.feeders
# token=../../kuksa.val/jwt/provide-all.token
# The example below works if you have cloned kuksa.val in parallel to kuksa-can-provider
# token=../kuksa.val/jwt/provide-all.token
# The example below works if you have cloned kuksa-coomon in parallel to kuksa-can-provider
# token=../kuksa-common/jwt/provide-all.token
# For KUKSA.val Server the default behavior is to use the token provided as part of kuksa-client
# So you only need to specify a different token if you want to use a different token
# Possibly like below
# token=../../kuksa.val/kuksa_certificates/jwt/super-admin.json.token
# token=../kuksa.val/kuksa_certificates/jwt/super-admin.json.token

# Definitions on what directions to support.
# Default is from CAN to KUKSA (dbc2val) only.
Expand Down

0 comments on commit 6f07ed1

Please sign in to comment.