Skip to content

Add RSU credentials to ODE configuration

Matt S edited this page Dec 19, 2018 · 3 revisions

Overview

The ODE now supports a default username and password configuration for RSU authentication.

This document is for users that would like to deposit, delete, or query messages on an RSU without including the credentials in the REST request JSON body. Storing them in the ODE's configuration is more secure.

Configuration

Notes:

  • These options are in decreasing order of precedence, as in having both option 1 and option 2 set means that option 1 will be the one used
  • Having the rsuUsername and rsuPassword fields set in the REST JSON body will override all of these
  • All RSUs must have the same username and password for this property to work
  • Do not include any quotation marks when setting the value

You may set the RSU username and password in one of three places:

  1. Set the environment variables ODE_RSU_USERNAME and ODE_RSU_PASSWORD on your local machine and then build the ODE as usual
  2. Set the environment variables in your .env file. See Using-the-.env-configuration-file for more information.
  3. Set the values in ode.rsuUsername and ode.rsuPassword in the file jpo-ode-svcs/src/main/resources/application.properties before the build or place a pre-configured application.properties file in the ODE working directory post-build (usually where DOCKER_SHARED_VOLUME points to).

Releases

Change Notices

Informational Reference

  • Decode a file with asn1c
  • Deposit BSM to S3
  • Docker fix for SSL issues due to corporate network
  • Docker management
  • ECDSA Primer
  • Filter BSMs through PPM module
  • Geofence Filtering for PPM
  • Import BSMs from RSU log file
  • Import TIMs from RSU log file
  • jpo security svcs Integration
  • Link host directory to Docker directory
  • Migrating from SDW websocket depositor to SDW Depositor Submodule
  • ODE Release Deployment
  • ODE Release Preparation
  • Prepare a fresh Ubuntu instance for ODE installation
  • Process for Handling Bugs (Code Defects)
  • Run the ODE using the ASN codec module
  • Query RSU for set TIMs
  • Schema Version 6 Change Notice
  • Signed Message File Import
  • TIM REST Endpoint Changes
  • Using the .env configuration file
  • Using the ODE test harness

Test Procedures

  • Delete TIM on RSU test
  • Event Logger Test
  • Import Decode and Deliver BSM Test
  • Manage SNMP Test
  • Sending PDM to RSU Test
  • Sending TIM to RSU Test
  • Submit_TIM_To_SDW Test

Archived

  • Log File Changes (schemaVersion=4)
  • Receive BSMs over UDP
  • Receive ISD via UDP and deposit to SDC
  • Receive VSD via UDP and deposit to SDC
  • Run the crypto test vectors code with ODE team's OSS encoder
  • SchemaVersion 5 Change Notice
Clone this wiki locally