Repository navigation
chore: bump certoagent to 0.0.6, send dataspaceIdentifier in cfm.issuer - #42
Merged
Merged
Conversation
certoagent 0.0.6 creates Certo participant contexts with
{participantContextId, did, dataspaceIdentifier}, reading the identifier
from the "dataspaceIdentifier" key of the cfm.issuer VPA properties, and
deletes them on dispose. The Membership Hub and the vendor stack's
create-participant.sh now send the DECADE-X-ID under that key instead of
"bpn".
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
wolf4ood
approved these changes
Oct 30, 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.
Requested by paul
Upgrades the Certo CFM agent from
0.0.3to0.0.6incharts/cx-veand in the vendor stack chart. That version includes eclipse-cfm/cfm#192:{participantContextId, did, dataspaceIdentifier}.The agent reads the identifier from the
dataspaceIdentifierkey of thecfm.issuerVPA properties. So the Membership Hub (DecadeXOnboarding.issuerProperties) andvendor-stack/scripts/create-participant.shnow send the DECADE-X-ID under that key.bpnis no longer sent, and there is no backwards compatibility. Certo tenants therefore carry the DECADE-X-ID, both in its flow-token check and in its NATS events.🤖 Generated with Claude Code