Bug Report
Describe the Bug
On 0.14.1 branch, I am unable to run the MVP demo i Intellij, because the IdentityHub fails (500) during seeding.
Expected Behavior
Seeding should complete.
Observed Behavior
I follow the readme instructions by staring NGINX and the services in IJ, via the supplied "dataspace" compound run configuration and ensure that they are running.
The connectors repeatedly log:
WARNING 2025-11-11T11:04:24.220163708 [DEMO] Error resolving DID: did:web:localhost%3A7083. HTTP Code was: 204
WARNING 2025-11-11T11:04:24.224579957 [DEMO] Error resolving DID: did:web:localhost%3A7093. HTTP Code was: 204
Since I have not done any seeding I assume that is fine, and its just warnings.
I manually run each step of the seed.sh script until:
curl -s --location 'http://localhost:7082/api/identity/v1alpha/participants/' --header 'Content-Type: application/json' --header "x-api-key: $API_KEY" --data "$DATA_CONSUMER"
That returns:
<html>
<head>...
<body>
<h2>HTTP ERROR 500 Internal Server Error</h2>
<table>
<tr><th>URI:</th><td>http://localhost:7082/api/identity/v1alpha/participants/</td></tr>
<tr><th>STATUS:</th><td>500</td></tr>
<tr><th>MESSAGE:</th><td>Internal Server Error</td></tr>
</table>
</body>
</html>
And in IdentityHub I now have the trace:
DEBUG 2025-11-11T11:19:59.76323887 Resolving secret super-user-apikey
DEBUG 2025-11-11T11:19:59.77203374 Storing secret did:web:localhost%3A7083-apikey
DEBUG 2025-11-11T11:19:59.772325565 Storing secret did:web:localhost%3A7083-sts-client-secret
Caused by: java.lang.NullPointerException: The curve must not be null
at java.base/java.util.Objects.requireNonNull(Objects.java:246)
at com.nimbusds.jose.jwk.ECKey$Builder.<init>(ECKey.java:263)
at com.nimbusds.jose.jwk.ECKey$Builder.<init>(ECKey.java:279)
at org.eclipse.edc.security.token.jwt.CryptoConverter.convertEcKey(CryptoConverter.java:354)
at org.eclipse.edc.security.token.jwt.CryptoConverter.createJwk(CryptoConverter.java:192)
at org.eclipse.edc.security.token.jwt.CryptoConverter.createJwk(CryptoConverter.java:167)
at org.eclipse.edc.identityhub.did.DidDocumentServiceImpl.lambda$keyPairActivated$16(DidDocumentServiceImpl.java:274)
at org.eclipse.edc.transaction.local.LocalTransactionContext.lambda$execute$0(LocalTransactionContext.java:57)
It appears to be did:web:localhost%3A7083-sts-client-secret that causes the problem.
If I re-run the curl command it only resolves the super-user-apikey and i get:
[{"message":"Another participant with the same DID 'did:web:localhost%3A7083' already exists.","type":"ObjectConflict","path":null,"invalidValue":null}]
So to reproduce, ensure that a sts-client-secret is attempted stored.
Can there be some state in the services that is not cleared by gradle clean? If so, how do I clean it?
Steps to Reproduce
Should just be checking out 0.14.1, starting it up and seeding.
Bug Report
Describe the Bug
On 0.14.1 branch, I am unable to run the MVP demo i Intellij, because the IdentityHub fails (500) during seeding.
Expected Behavior
Seeding should complete.
Observed Behavior
I follow the readme instructions by staring NGINX and the services in IJ, via the supplied "dataspace" compound run configuration and ensure that they are running.
The connectors repeatedly log:
Since I have not done any seeding I assume that is fine, and its just warnings.
I manually run each step of the seed.sh script until:
That returns:
And in IdentityHub I now have the trace:
It appears to be did:web:localhost%3A7083-sts-client-secret that causes the problem.
If I re-run the curl command it only resolves the super-user-apikey and i get:
So to reproduce, ensure that a sts-client-secret is attempted stored.
Can there be some state in the services that is not cleared by gradle clean? If so, how do I clean it?
Steps to Reproduce
Should just be checking out 0.14.1, starting it up and seeding.