Skip to content
Documentation Menu

TC_073_CS — Update Charge Point Password for HTTP Basic Authentication

TC_073_CS — Update Charge Point Password for HTTP Basic Authentication

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 96.

Identification

FieldValue
Test case nameUpdate Charge Point Password for HTTP Basic Authentication
Test case IdTC_073_CS
System under testCharge Point

Description

The Central System can configure a new password for HTTP Basic Authentication, the Central System can send a new value for the BasicAuthPassword Configuration key.

Purpose

To check if the Charge Point is able to switch to a new Basic Authentication password.

Prerequisite(s)

The Charge Point supports Security profile 1 and/or 2.

Before (Preparations)

Configuration State(s):

  • N/a

Memory State(s):

  • N/a

Reusable State(s):

  • N/a

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
2. The Charge Point responds with a ChangeConfiguration.conf1. The Central System sends a ChangeConfiguration.req
3. The Charge Point disconnects its current connection and reconnects to the Central System with the new password.
5. The Charge Point responds with a ChangeConfiguration.conf4. The Central System sends a ChangeConfiguration.req
6. The Charge Point disconnects its current connection and reconnects to the Central System with the new password.

Tool validation(s)

Charge Point side:

Step 2:

(Message: ChangeConfiguration.conf) status is Accepted

Step 3:

The Charge Point reconnects to the Central System with the new password.

Step 5:

(Message: ChangeConfiguration.conf) status is Accepted

Step 6:

The Charge Point reconnects to the Central System with the new password.

Central System side:

Step 1:

(Message: ChangeConfiguration.req) key is AuthorizationKey value is 4F43415F4F4354545F61646D696E5F74657374 ("OCA_OCTT_admin_test" HexEncoded)

Step 4:

(Message: ChangeConfiguration.req) key is AuthorizationKey value contains a randomly generated binary of 20 bytes represented as a string of 40 hexadecimal digits.

Expected result(s) / behaviour

Charge Point side:

  • N/a

Central System side:

  • N/a