CH integrated tests fail #29
Comments
|
Hello Christos, <bean id="rootDaps" class="de.fhg.aisec.ids.idscp2.beans.AisecDapsDriverFactoryBean">
<property name="dapsUrl" value="${connector.daps-url}"/>
<property name="dapsSslParameters" ref="rootClientSslContext" />
<property name="transportCertificatesParameters" ref="rootClientSslContext" />
</bean>
ids-multipart:
daps-bean-name: rootDapsWhen doing this properly, the AISEC DAPS driver should pick up your transport certificate and include its actual fingerprint into the DAT request, hopefully resulting in a DAT with the right fingerprint. Good luck! |
|
Thank you for your quick response. Under intTest folder there are two packages. One for idsp2 and one for multipart. Thanks to your advices and taking a close look at code of integration tests we manage to pass the tests are relevant to multipart. However, the tests are related to idscp2 communication failed again. Logs from tests: Logs from TC The environment in which we conducted our attempts is an Ubuntu 20.04 instance running on WSL (Windows Subsystem for Linux). |
|
The hostname verification failed. In the multipart-case no hostname verification is done to check whether or not the client is a valid connector. This is not the case with idscp2. The client is validated and it is checked that the hostname in the certificate of the client is correct. Since this check was included in the TC the tests cannot be run as they are on a test setup. They require a registered connector with a valid hostname and domain, which makes running the idscp2 tests correctly rather difficult. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
My name is Christos Aslamatzidis from European Dynamics S.A. We try to test and configure the Clearing House Service because of the need to explore it and implement it in a project called Enershare.
So far, we have followed the documentation and we have deployed the CH.
Our docker-compose.yaml is this :
Running the above docker-compose all containers start without issues.
Our next though was to test our deployment using the integration tests that were provided in Clearing House Processors following the documentation
Please note that we have changed the host from
to
Watching Closely the code of clearing house we observe that provider-core has been replaced with tc-core-server. After this modification we were able to reach in some point our CH installation ; however integrated tests fail.
below are the logs of our tests:
The common error is this:
The logs of TC :
The logs of logging Service :
The above logs are indicative parts of the our actual logs.
If you need entire logs please inform me.
What we are missing to pass the tests successfully?
In some point I can understand that the errors are relevant with certificates.
In docker-compose, we use service-keystore.p12 and truststore.p12 existing under clearing-house-processor in intTest folder.
Also we have try both https://daps-dev.aisec.fraunhofer.de/ and https://daps.aisec.fraunhofer.de/ in many versions (v3 ,v4).
We will appreciate your help for resolving this issue and your support to make the next steps to be closer to a production CH environment.
Thank you in advance.
The text was updated successfully, but these errors were encountered: