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

Unable to publish DID document warning Printed When Activating ParticipantContext at Creation (isActive=true) #480

Open
thomasrutger opened this issue Oct 16, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@thomasrutger
Copy link
Contributor

Bug Report

Describe the Bug

When creating a ParticipantContext with ParticipantManifest.isActive=true, a warning is printed:

WARNING [DidDocumentService] Updating DID documents after activating a KeyPair failed: Cannot publish DID 'did:web:alice' for participant 'alice' because the ParticipantContext state is not 'ACTIVATED', but 'CREATED'.

This is because the key pair is added first before activating the Participant (which invokes a did document update). The ParticipantContext is activated afterwards and as a result, the DID document will still be published, but the warning is printed regardless.

Expected Behavior

I expect no warning when directly activating a ParticipantContext at creation.

Observed Behavior

The aforementioned warning is printed.

Steps to Reproduce

Create a ParticipantManifest with .active(true), then create the ParticipantContext

Context Information

Add any other context about the problem here.

Detailed Description

If applicable, add screenshots and logs to help explain your problem.

Possible Implementation

Activate the participant (if the manifest has isActive=true) before adding the key pair. Perhaps directly while building the ParticipantContext.

@github-actions github-actions bot added the triage all new issues awaiting classification label Oct 16, 2024
Copy link

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale label Oct 31, 2024
@ndr-brt ndr-brt added bug Something isn't working and removed stale triage all new issues awaiting classification labels Oct 31, 2024
@paullatzelsperger paullatzelsperger self-assigned this Nov 6, 2024
Copy link

github-actions bot commented Dec 5, 2024

This issue is stale because it has been open for 28 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants