TC_085_CS — Basic Authentication - Valid username/password combination

TC_085_CS — Basic Authentication - Valid username/password combination

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

Identification

Field	Value
Test case name	Basic Authentication - Valid username/password combination
Test case Id	TC_085_CS
System under test	Charge Point

Description

The Charge Point uses Basic authentication to authenticate itself to the Central System, when using security profile 1 or 2.

Purpose

To verify whether the Charge Point is able to authenticate itself to the Central System using Basic Authentication.

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)

• N/a

Tool validation(s)

Charge Point side:

Step 1:

The authorization header of the HTTP upgrade request must be formatted as follows: AUTHORIZATION: Basic <Base64 encoded(<ChargePointId>:<Configured (non hex representation of) BasicAuthPassword>)>

• The ChargePointId, must equal the ChargePointId provided at the end of the connection url string of the HTTP request. Note: The BasicAuthPassword can be configured in two ways:

1. When the configured value for BasicAuthPassword is >= 32 and ⇐ 40 characters, the tool will expect that this is the hex encoded representation of the password.
2. When the configured value for BasicAuthPassword is >= 16 and ⇐ 20 characters, the tool will expect that this is plaintext (UTF-8) representation of the password. Post scenario validations: N/a

Central System side:

• N/a

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

• N/a