Repository navigation
feat: enforce participant context state on dsp layer - #6142
Merged
wolf4ood merged 2 commits intoOct 21, 2026
Merged
Conversation
wolf4ood
marked this pull request as ready for review
October 21, 2026 14:46
jimmarino
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR changes/adds
ParticipantContextServicegetsactivateParticipantContextanddeactivateParticipantContext.updateParticipantContextkeeps the stored state, so a PUT no longer resets it toCREATED.ParticipantContext.toBuilder()now copies theidentity. It was missing, which madetoBuilder().build()fail.management-api:admin):POST /v5/participants/{id}/activate;POST /v5/participants/{id}/deactivate.DEACTIVATEDparticipant context is answered with 404, like one that does not exist:DspVirtualProfileDispatcher, which covers catalog, negotiations and transfers;/.well-known/dspace-version.Why it does that
The participant context state was not enforced and could not be managed: only the management API authentication
filter checked
DEACTIVATED(#6124), and any update reset the state (M5 in #6005).Further notes
DEACTIVATEDblocks:CREATEDkeeps behaving as operational.processes, and they continue if the participant context is activated again.
ParticipantContextServicehas two new methods. Custom implementations need to add them.Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Linked Issue(s)
Part of #6005
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.