Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Authentication 'super-user' when running seed.sh #293

Closed
darrylestrada97 opened this issue Jul 16, 2024 · 4 comments
Closed

Invalid Authentication 'super-user' when running seed.sh #293

darrylestrada97 opened this issue Jul 16, 2024 · 4 comments
Labels

Comments

@darrylestrada97
Copy link

Bug Report

Describe the Bug

After running the dataspace run config in Intellij, I tried running the seed.sh file, the response from the file is.

Create consumer participant
[{"message":"Invalid Authentication 'super-user': ParticipantContext with ID 'super-user' does not exist.","type":"AuthenticationFailed","path":null,"invalidValue":null}]

Create provider participant
[{"message":"Invalid Authentication 'super-user': ParticipantContext with ID 'super-user' does not exist.","type":"AuthenticationFailed","path":null,"invalidValue":null}]
  • Used version: 0.8.1-SNAPSHOT
  • OS: Ubuntu 20
  • Java temurin-21
@paullatzelsperger
Copy link
Member

can you try by running all the individual run configs separately? what happens then?

@darrylestrada97
Copy link
Author

darrylestrada97 commented Jul 17, 2024

Hi! when running the scrips one by one there are the responses.

Connector "provider-manufacturing"
DEBUG 2024-07-17T09:40:53.770224163 [ExecutionManager] Run pre-execution task
DEBUG 2024-07-17T09:40:53.770404471 [ExecutionManager] No WorkItems found, skipping execution
DEBUG 2024-07-17T09:40:53.770224163 [ExecutionManager] Run pre-execution task
DEBUG 2024-07-17T09:40:53.770404471 [ExecutionManager] No WorkItems found, skipping execution
DEBUG 2024-07-17T09:40:53.770224163 [ExecutionManager] Run pre-execution task
DEBUG 2024-07-17T09:40:53.770404471 [ExecutionManager] No WorkItems found, skipping execution

Connector Consumer Corp.

DEBUG 2024-07-17T09:43:05.638174294 [DataPlaneSelectorManagerImpl] DataPlaneInstance consumer-embedded-runtime is now in state AVAILABLE
DEBUG 2024-07-17T09:43:09.60740741 [ExecutionManager] Run pre-execution task
DEBUG 2024-07-17T09:43:09.607540487 [ExecutionManager] No WorkItems found, skipping execution

Connector "provider-qna"

DEBUG 2024-07-17T09:43:46.102522221 [ExecutionManager] No WorkItems found, skipping execution
DEBUG 2024-07-17T09:43:56.102321238 [ExecutionManager] Run pre-execution task
DEBUG 2024-07-17T09:43:56.102513807 [ExecutionManager] No WorkItems found, skipping execution
DEBUG 2024-07-17T09:44:06.102411791 [ExecutionManager] Run pre-execution task
DEBUG 2024-07-17T09:44:06.102687346 [ExecutionManager] No WorkItems found, skipping execution

IdentityHub Consumer Corp

INFO 2024-07-17T09:43:43.776093153 Started DID management Identity API Extension
INFO 2024-07-17T09:43:43.776121165 Started ParticipantContext management Identity API Extension
INFO 2024-07-17T09:43:43.776151016 Started Identity API Authentication Extension
INFO 2024-07-17T09:43:43.777223797 Runtime 80867617-0916-4771-a57e-369ac37e66d8 ready

IdentityHub Provider Corp

WARNING 2024-07-17T09:44:33.786335359 A service of the type java.time.Clock was already registered and has now been replaced with a SystemClock instance.
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
....
...
..
INFO 2024-07-17T09:44:34.500387955 Started Presentation API Extension
INFO 2024-07-17T09:44:34.500413571 Started DID management Identity API Extension
INFO 2024-07-17T09:44:34.500440281 Started ParticipantContext management Identity API Extension
INFO 2024-07-17T09:44:34.500465485 Started Identity API Authentication Extension
INFO 2024-07-17T09:44:34.501273614 Runtime 42e249df-79a8-415e-9d6a-0437cc29954e ready

Provider Catalog Server
INFO 2024-07-17T09:45:55.591101314 Using the Embedded STS client, as no other implementation was provided.
WARNING 2024-07-17T09:45:55.59394947 The JTI Validation rule is not yet implemented as it depends on eclipse-edc/Connector#3749.
INFO 2024-07-17T09:45:55.595185083 Initialized org.eclipse.edc.iam.identitytrust.core.IdentityAndTrustExtension
INFO 2024-07-17T09:45:55.607541288 Initialized org.eclipse.edc.iam.identitytrust.core.IdentityTrustTransformExtension
WARNING 2024-07-17T09:45:55.614034495 No TransactionContext registered, a no-op implementation will be used, not suitable for production environments
WARNING 2024-07-17T09:45:55.628808068 No TokenDecorator was registered. The 'scope' field of outgoing protocol messages will be empty
...
...
...
INFO 2024-07-17T09:45:56.295987702 Started Dataspace Protocol Negotiation Transform Extension
INFO 2024-07-17T09:45:56.296023083 Started Dataspace Protocol Transfer HTTP Dispatcher Extension
INFO 2024-07-17T09:45:56.296057715 Started org.eclipse.edc.protocol.dsp.transferprocess.http.api.DspTransferProcessApiExtension
INFO 2024-07-17T09:45:56.296105488 Started Dataspace Protocol Transfer Process Transform Extension
INFO 2024-07-17T09:45:56.297447404 Runtime faece5c7-ac02-43fa-82e0-71ce075e1597 ready

I ran them one by one in the order I wrote them.

the seed.sh is still throwing the same message.

Create consumer participant
[{"message":"Invalid Authentication 'super-user': ParticipantContext with ID 'super-user' does not exist.","type":"AuthenticationFailed","path":null,"invalidValue":null}]

Create provider participant
[{"message":"Invalid Authentication 's

@darrylestrada97
Copy link
Author

darrylestrada97 commented Jul 17, 2024

I found a solution to this issue, I had to manually build the extensions:superuser-seed project, and then run the dataspace config and finally the seed.sh, now it works.

@paullatzelsperger
Copy link
Member

solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants