The serviceUri attribute in test 7.3.2.s1. wrongly expects the port number to be included when it is 443 or 80
Description
The serviceUri attribute is defined as "The fully qualified URI to a Deployment Management server for O2dms services. Since the O2dms provides multiple services, this entry is for the {apiRoot} only."
The test 7.3.2.s1 expects the serviceUri attribute when querying the inventory to follow the structure (protocol+hostname/IP+port):
However, this could not be true when the O2IMS API listens in default HTTP and/or HTTPS. If the serviceUri is HTTP or HTTPs and does not include the 80/tcp or 443/tcp port is agreed that the port is the default (well-known) one and then the serviceUri does not have to include the port number. I can't find in the specification (see definition of the attribute) that the port must be included if it is the default port for the HTTP/HTTPS protocol.
Our product does not include the port of the serviceUri if the interface is exposed in HTTP or HTTPs and that could be the case for several other products.
I propose to check in the conformance test if the port defined in the configuration.yaml is 80 or 443. Then the verification of the serviceUri is against both cases: the protocol+hostname/ip+port (as it is now) and protocol+hostname/ip so both cases are covered and the test should not fail if the well-known port is not included.
Medium
The serviceUri attribute is defined as "The fully qualified URI to a Deployment Management server for O2dms services. Since the O2dms provides multiple services, this entry is for the {apiRoot} only."
The test 7.3.2.s1 expects the serviceUri attribute when querying the inventory to follow the structure (protocol+hostname/IP+port):
However, this could not be true when the O2IMS API listens in default HTTP and/or HTTPS. If the serviceUri is HTTP or HTTPs and does not include the 80/tcp or 443/tcp port is agreed that the port is the default (well-known) one and then the serviceUri does not have to include the port number. I can't find in the specification (see definition of the attribute) that the port must be included if it is the default port for the HTTP/HTTPS protocol.
Our product does not include the port of the serviceUri if the interface is exposed in HTTP or HTTPs and that could be the case for several other products.
I propose to check in the conformance test if the port defined in the configuration.yaml is 80 or 443. Then the verification of the serviceUri is against both cases: the protocol+hostname/ip+port (as it is now) and protocol+hostname/ip so both cases are covered and the test should not fail if the well-known port is not included.
Here you can find the fix proposed: