consent-manager

Published automatically.

Repository: github.com/OpenG2P/consent-manager · Container images: Container Registry

Releases

consent-manager 1.0.3 — 2026-09-04

commit b83b37c · changes since release 1.0.2

Same artifact as 1.0.3-rc.63 — built from the same commit and promoted (retagged), not rebuilt. No code changed between them.

Chart: openg2p-consent-manager 1.0.3

Release notes

What's Changed

• Bump version to 1.0.3 and update image tags to 1.0.3 by @vin0dkhichar in https://github.com/OpenG2P/consent-manager/pull/7

New Contributors

• @vin0dkhichar made their first contribution in https://github.com/OpenG2P/consent-manager/pull/7

Full Changelog: https://github.com/OpenG2P/consent-manager/compare/1.0.2...1.0.3

Summary

• Version update: bumped to 1.0.3 and updated image tags accordingly.

Changes

• Bump version to 1.0.3 and update image tags to 1.0.3 (2d9357e)

consent-manager 1.0.2 — 2026-09-01

commit 52bb1b0 · changes since release 1.0.1

Same artifact as 1.0.2-rc.61 — built from the same commit and promoted (retagged), not rebuilt. No code changed between them.

Chart: openg2p-consent-manager 1.0.2

Release notes

What's Changed

• Update image tags to version 1.0.2 by @mkumar-02 in https://github.com/OpenG2P/consent-manager/pull/6

Full Changelog: https://github.com/OpenG2P/consent-manager/compare/1.0.1...1.0.2

Summary

• Dependency update: upgraded image tags to version 1.0.2 for improved performance and security.

Changes

• Update image tags to version 1.0.2 (8bce8bc)

consent-manager 1.0.1 — 2026-09-01

commit c84a6dd · changes since release 1.0.0

Same artifact as 1.0.1-rc.59 — built from the same commit and promoted (retagged), not rebuilt. No code changed between them.

Chart: openg2p-consent-manager 1.0.1

Release notes

Updated

• keycloak-init version to 1.2.0
• fastapi-common version set to 1.2.0

Summary

• Dependency updates: upgraded FASTAPI_COMMON_REF and keycloak-init to version 1.2.0, ensuring compatibility with the latest features and fixes.

Changes

• Update FASTAPI_COMMON_REF to version 1.2.0 (c84a6dd)
• Update keycloak-init version to 1.2.0 (167a49e)

consent-manager 1.0.0 — 2026-09-01

commit c67030b · first release

Same artifact as 1.0.0-rc.57 — built from the same commit and promoted (retagged), not rebuilt. No code changed between them.

Chart: openg2p-consent-manager 1.0.0

Release notes

Consent Manager 1.0.0 First production-ready release of the OpenG2P Consent Manager (CM): a dedicated Policy Decision Point for outbound data sharing.

No personal data leaves a registry (or any other data-holding module) without a positive CM decision. The registry stays a Policy Enforcement Point — it never interprets consent, never holds partner signing keys, and never evaluates policy.

One CM instance is shared across modules (registry, PBMS, and others). Partner identity and keys live in Partner Management; CM holds only a thin policy binding.

Documentation: docs.openg2p.org → Consent Management

Highlights

• Verify & enforce — partners embed a compact JWS consent object; CM verifies the signature against Partner Management keys, evaluates the partner’s data-share policy, and returns the effective fields the PEP may release (consent ∩ policy).
• Cryptographic proof — partner-signed consent objects; CM-signed Kantara/ISO 27560-aligned receipts published at /.well-known/jwks.json.
• Versioned partner policy — allowed fields, purposes, subject ID types, signing algorithms, validity ceiling, and fetch semantics. Policy widening can be gated by the Approval Workflow Engine (AWE).
• Consent origination — request → OIDC authenticate → approve/deny → artefact + receipt, plus revocation and scheduled expiry.
• Staff console — partner policy bindings, an AWE approvals inbox, and an immutable decision log.
• Platform-ready deploy — Helm chart with staff + partner APIs (beneficiary API scaffolded), Keycloak and Postgres init, Istio routing, HPA, signing-key Secret, expiry CronJob, and a release-blocking sanity Job.

Links

• Source: https://github.com/OpenG2P/consent-manager
• Design & API: https://docs.openg2p.org/platform/platform-services/consent-management
• License: Mozilla Public License 2.0

Summary

• Major: Migration to GitLab: repository moved from GitHub, with updated README to reflect the change and disabled auto build/publish on GitHub.
• CI/CD enhancements: replaced docker-build and helm-publish with a centralized build-publish workflow, and published consent-manager images and charts exclusively to GitLab.
• Job configuration fixes: resolved duplicate environment variable issues in the cm-sanity Job and added nameOverride for better alignment with renamed API components.
• Keycloak updates: new location and version adjustments implemented for Keycloak initialization.

Changes

• G2P-5605 Build and publish on GitHub again (c67030b)
• Keycloak-init new location and version updated. (a434f9b)
• G2P-5222 Point image source and project URLs at the new GitLab location (openg2p/platform-services/consent-manager). (81e8fd6)
• G2P-5575 Changes applied the platform-service group change on consent-manager (9b09d4c)
• Fix duplicate SANITY_VERIFY_TLS env in the cm-sanity Job (emitted both inline and via the shared pmSeedEnv helper), which made server-side apply reject the Job with "duplicate entries for key" and fail the release (a9f7c06)
• The sanity and pm-seed Jobs hardcoded <release>-sanity / <release>-pm-seed, so when the API components are renamed via nameOverride the sanity Job name no longer lines up with them. Add sanity.nameOverride (default "" = no change) inserted as an infix: e.g. "cm" -> <release>-cm-sanity / <release>-cm-pm-seed. (954ee5f)
• Minor edit to just stimulate helm publish. (64fa696)
• G2P-5222 Freeze GitHub repo: add "moved to GitLab" README notice and disable auto build/publish (remove push/tag triggers). (d826db5)
• G2P-5335 Re-run GitLab pipeline with fixed chart job (51fd07c)
• G2P-5348 Minor edit of README. (58f81a4)
• G2P-5335 Minor edit of README. (f87a6ea)
• G2P-5348 Moved repo from Github as is. (8bf5787)
• G2P-5335 Grant packages: write in caller to satisfy reusable workflow (fix startup failure) (88041e0)
• G2P-5335 Publish consent-manager images and chart to GitLab; drop GHCR (b38f1e7)
• G2P-5335 consent-manager: publish images + chart to GHCR (chart under charts/ to avoid image name clash) (b736910)
• G2P-5335 Publish images + chart to GHCR only (OCI), values to ghcr.io (6f7508a)
• G2P-5335 clarify changelog workflow_dispatch input descriptions (326edee)
• G2P-5335 forward changelog dispatch inputs to central workflow (75b649f)
• G2P-5335 Fix in publish. (9ff69b6)
• G2P-5335 ci: replace docker-build + helm-publish with central build-publish workflow (0a508a6)

Release candidates

consent-manager 1.0.3-rc.63 — 2026-09-04

commit b83b37c · changes since 0.0.0-develop.57

Chart: openg2p-consent-manager 1.0.3-rc.63

Summary

• Version updates: bumped to 1.0.3, with image tags updated accordingly; FASTAPI_COMMON_REF and keycloak-init upgraded to versions 1.2.0.

Changes

• Bump version to 1.0.3 and update image tags to 1.0.3 (2d9357e)
• Update image tags to version 1.0.2 (8bce8bc)
• Update FASTAPI_COMMON_REF to version 1.2.0 (c84a6dd)
• Update keycloak-init version to 1.2.0 (167a49e)

consent-manager 1.0.2-rc.61 — 2026-09-01

commit 52bb1b0 · changes since 0.0.0-develop.57

Chart: openg2p-consent-manager 1.0.2-rc.61

Summary

• Dependency updates: upgraded image tags to version 1.0.2, FASTAPI_COMMON_REF to version 1.2.0, and keycloak-init to version 1.2.0.

Changes

• Update image tags to version 1.0.2 (8bce8bc)
• Update FASTAPI_COMMON_REF to version 1.2.0 (c84a6dd)
• Update keycloak-init version to 1.2.0 (167a49e)

consent-manager 1.0.1-rc.59 — 2026-09-01

commit c84a6dd · changes since 1.0.1-rc.58

Chart: openg2p-consent-manager 1.0.1-rc.59

Changes

• Update FASTAPI_COMMON_REF to version 1.2.0 (c84a6dd)

consent-manager 1.0.1-rc.58 — 2026-09-01

commit 167a49e · changes since 0.0.0-develop.57

Chart: openg2p-consent-manager 1.0.1-rc.58

Changes

• Update keycloak-init version to 1.2.0 (167a49e)

consent-manager 1.0.0-rc.57 — 2026-09-01

commit c67030b · changes since 0.0.0-develop.57

Chart: openg2p-consent-manager 1.0.0-rc.57

Changes

No new commits since 0.0.0-develop.57.

Develop builds

consent-manager — develop 0.0.0-develop.76 (2026-10-13)

commit b69fa58 · changes since 0.0.0-develop.75

Chart: openg2p-consent-manager 0.0.0-develop.76

Changes

• G2P-5719 "consent token" for the exchange's per-query, per-registry token in form labels, chart comments, docstrings and OpenAPI descriptions (API fields, settings and messages unchanged; the consent receipt document keeps its name) (b69fa58)

consent-manager — develop 0.0.0-develop.75 (2026-10-13)

commit f48f34e · changes since 0.0.0-develop.74

Chart: openg2p-consent-manager 0.0.0-develop.75

Changes

• G2P-5719 CM chart: .p12 password read from the key's Secret unless set separately; required subject identifiers accept a comma-separated string (Rancher); form fields for the national-ID login and required identifiers; partner portal form text points to setup-partner-realm.sh (f48f34e)

consent-manager — develop 0.0.0-develop.74 (2026-10-13)

commit 69cd69c · changes since 0.0.0-develop.72

Chart: openg2p-consent-manager 0.0.0-develop.74

Summary

• Major: Assisted consent feature enhancement: support for additional subject identifiers (e.g., FARMER_ID) in requests and consents, with visibility in the portal and staff page, and mandatory confirmation by approvers in the registry.
• Evidence bucket creation streamlined through the commons-base Garage init job, reducing manual steps for older commons versions.
• National-ID login demographics are now displayed with clear source labels, ensuring no comparisons are made between identifiers.
• Comprehensive testing implemented for the new consent features to ensure reliability and compliance.

Changes

• G2P-5719 CM chart: the evidence bucket is created by the commons-base Garage init job (manual step only for older commons) (69cd69c)
• G2P-5719 assisted consent: other subject identifiers (e.g. FARMER_ID) on requests and consents — required per deployment (partnerPortal.requiredSubjectIdentifiers), shown in the portal, staff page, consent and consent record; approver must confirm them in the registry (recorded in assurance); national-ID login demographics shown labelled with their source, never compared; tests (262e80c)

consent-manager — develop 0.0.0-develop.72 (2026-10-12)

commit ba467f4 · changes since 0.0.0-develop.69

Chart: openg2p-consent-manager 0.0.0-develop.72

Summary

• National-ID login enhancement: implemented userinfo JWT validation against the registry's VC flow, including checks for aud and sub, with support for both published and unpublished signing keys.
• User experience improvements: redesigned partner portal interface with a new layout featuring a black left pane, full logo, and an icon-based menu, utilizing lucide-react icons for better visual consistency.
• Testing updates: added comprehensive tests to mirror eSignet's responses for national-ID login scenarios, ensuring robust validation of JWT handling and user authentication flows.

Changes

• G2P-5719 national-ID login, checked against the registry's VC flow and the mock identity system: the userinfo JWT (identity system's key and own iss, aud = client, no exp) accepted as fetched over HTTPS with aud and sub checked; a callback that never finished reads as failed; tests mirror eSignet's answer (ba467f4)
• G2P-5719 national-ID login: a userinfo JWT signed with a key eSignet does not publish (the identity system's) is accepted as fetched over HTTPS with the access token (OIDC Core 5.3.2), with iss/aud/exp/sub still checked; signature checked when the key is published; tests (c612b99)
• G2P-5719 partner portal: OpenG2P shell as in the Master Data UI — black left pane with the full logo and "Partner Portal", menu with icons, user and sign-out at the bottom (top bar on phones); lucide-react icons (382dfdb)

consent-manager — develop 0.0.0-develop.69 (2026-10-12)

commit 3b4d78f · changes since 0.0.0-develop.68

Chart: openg2p-consent-manager 0.0.0-develop.69

Changes

• G2P-5719 /validate: a request with neither or both of consent_jws / consent_id is a 200 deny (malformed_object), not a 400 — the partner api's contract (CM sanity contract test failed on install) (3b4d78f)

consent-manager — develop 0.0.0-develop.68 (2026-10-12)

commit 1545ade · changes since 0.0.0-develop.65

Chart: openg2p-consent-manager 0.0.0-develop.68

Summary

• Major: New consent record download feature for partners, providing a ZIP file with the original receipt, uploaded evidence, and a CM-signed statement, with SHA-256 verification against national-ID authentication.
• Enhanced national-ID login integration in the partner portal, utilizing authorization code + PKCE, private_key_jwt, and individual ID matching, now mandatory for submission and approval processes.
• Improved handling of CM approvals inbox when AWE approvals are disabled, displaying an empty list instead of a 404 error, with appropriate messaging in the console.
• Comprehensive testing added for new features, ensuring robustness and compliance with security standards.

Changes

• G2P-5719 partner's copy of a consent: "Download consent record" (GET …/partner-portal/consents/{id}/record) — a ZIP with the unchanged receipt, the uploaded evidence, a CM-signed statement (same key/JWKS) tying them together by SHA-256 with the national-ID authentication and the verification time, a printable summary and how to check it; refused if stored evidence no longer matches its SHA-256; chart partnerPortal.consentRecordJwksUrl; tests (1545ade)
• G2P-5719 consent scenario 1 phase 2: the subject's national-ID login (eSignet) in the partner portal — authorization code + PKCE, private_key_jwt, single-use state in Postgres, ID token and signed userinfo checked (signature, iss, aud, exp, nonce, sub), individual_id matched to the request's subject; mandatory when on (submit and approve need it, with the signed form and staff check); assurance records it; portal "Authenticate with national ID" (popup + polling), console shows it on verification; chart partnerPortal.subjectAuth (off by default) with a Job that keeps the client key in a Secret and registers the client in eSignet; tests (0115010)
• G2P-5719 CM approvals inbox when AWE approvals are off: empty list with awe_enabled false instead of AWE's 404 (AWE need not be installed); console Approvals page says approvals are off; test (7d49c45)

consent-manager — develop 0.0.0-develop.65 (2026-10-10)

commit 1e29e4b · changes since 0.0.0-develop.64

Chart: openg2p-consent-manager 0.0.0-develop.65

Changes

• G2P-5719 consent scenario 1 (phase 1): partner realm auth, partner-portal API and SPA (requests, signed-form evidence in Garage, submit/cancel, consents and receipts, use-case prefill), staff "Consent verifications" in the console, assurance on consents, /validate by consent_id with receipts and grants; chart partnerPortal/evidence (off by default) + partner keycloak-init; setup-partner-realm.sh; CI builds the portal image (1e29e4b)

consent-manager — develop 0.0.0-develop.64 (2026-10-07)

commit 8e9ef7b · changes since 0.0.0-develop.63

Chart: openg2p-consent-manager 0.0.0-develop.64

Changes

• G2P-5719 CM exchange receipts (opt-in, off by default): issue_receipts on /validate signs one consent receipt per controller for configured presenters with the CM signing key; GET /receipts/{jti}/status (revoked with the consent, expired by time); department role accepts receipts from trusted issuers (JWKS cache + unknown-kid refresh, aud/presenter/time, status check, standing policy for the presenter, scopes intersected) and logs receipt jti/issuer; chart values + Rancher "Agri Stack exchange" group; tests (8e9ef7b)

consent-manager — develop 0.0.0-develop.63 (2026-10-05)

commit b6950f1 · changes since 0.0.0-develop.61

Chart: openg2p-consent-manager 0.0.0-develop.63

Summary

• Major: Policy form enhancements: server-side validation for policy fields, binding status, and decision filters; new signing algorithms as checkboxes and fetch type/durations as pickers; invalid values flagged via issues.
• AWE approvals: enabled via a seed job for the approval policy, with admin token forwarding, callback URL configuration, and support for failed/stale states.
• Improved user experience: resubmit endpoint and UI for pending versions, along with inbox lists for open and claimed tasks.
• Testing improvements: comprehensive tests added for new features and validations, ensuring robust functionality.

Changes

• G2P-5719 Policy form selects fed by GET /consent/v1/meta with server-side validation; clearing an "any when empty" list counts as widening; AWE approvals ready to enable (still off by default): seed job seeds the approval policy, admin token forwarded with external-issuer fallback, callback URL from the staff API service name, failed/stale states, one pending version per binding, resubmit endpoint + UI, configurable hook annotations, inbox lists open and claimed tasks, AWE error parsing, requester, fetch type/interval count as widening, first-policy gate configurable; tests (b6950f1)
• G2P-5719 Policy form: signing algs as checkboxes, fetch type and durations as pickers fed by GET /consent/v1/meta; policy fields, binding status and decision filter validated server-side; stored invalid values load flagged via issues; clearing an "any when empty" list (purposes, subject ID types, signing algs) now counts as widening and needs approval; tests (b01788d)

consent-manager — develop 0.0.0-develop.61 (2026-10-02)

commit 21e817a · changes since 0.0.0-develop.60

Chart: openg2p-consent-manager 0.0.0-develop.61

Changes

• G2P-5719 Pin sqlalchemy[asyncio] <2.1: the image died at import without greenlet (21e817a)

consent-manager — develop 0.0.0-develop.60 (2026-10-01)

commit c6c6382 · changes since 0.0.0-develop.59

Chart: openg2p-consent-manager 0.0.0-develop.60

Changes

• G2P-5719 Return a stored consent decision only after the binding and signature check, and only for the same consent (reused jti → replay); tests; .env.example wording (c6c6382)

consent-manager — develop 0.0.0-develop.59 (2026-10-01)

commit 87648fe · changes since 0.0.0-develop.58

Chart: openg2p-consent-manager 0.0.0-develop.59

Changes

• G2P-5719 Single consent with one grant per registry: grants claim, data_controller on /validate, bindings per (partner, controller), replay per (jti, controller), subject_mismatch, consent requests with grants, UI, tests (87648fe)

consent-manager — develop 0.0.0-develop.58 (2026-09-01)

Note — Marking this working version before major changes are don

commit 5361069 · changes since 0.0.0-develop.57

Chart: openg2p-consent-manager 0.0.0-develop.58

Changes

• Change FASTAPI_COMMON_REF to version 1.2.0 (5361069)

consent-manager — develop 0.0.0-develop.57 (2026-08-28)

commit c67030b · changes since the start (showing the latest 20 commits)

Chart: openg2p-consent-manager 0.0.0-develop.57

Summary

• Major: Migration to GitLab: repository moved from GitHub, with updated README to reflect the change and disabled auto build/publish on GitHub.
• CI/CD enhancements: implemented a central build-publish workflow, replacing the previous docker-build and helm-publish processes; fixed chart job in GitLab pipeline.
• Image and chart publishing: consent-manager images and charts are now published exclusively to GitLab, with adjustments to avoid name clashes and ensure proper versioning.
• Environment variable fix: resolved duplicate SANITY_VERIFY_TLS environment variable issue in the cm-sanity Job, preventing job failures.
• Job name alignment: introduced sanity.nameOverride to ensure consistency in job naming when API components are renamed.

Changes

• G2P-5605 Build and publish on GitHub again (c67030b)
• Keycloak-init new location and version updated. (a434f9b)
• G2P-5222 Point image source and project URLs at the new GitLab location (openg2p/platform-services/consent-manager). (81e8fd6)
• G2P-5575 Changes applied the platform-service group change on consent-manager (9b09d4c)
• Fix duplicate SANITY_VERIFY_TLS env in the cm-sanity Job (emitted both inline and via the shared pmSeedEnv helper), which made server-side apply reject the Job with "duplicate entries for key" and fail the release (a9f7c06)
• The sanity and pm-seed Jobs hardcoded <release>-sanity / <release>-pm-seed, so when the API components are renamed via nameOverride the sanity Job name no longer lines up with them. Add sanity.nameOverride (default "" = no change) inserted as an infix: e.g. "cm" -> <release>-cm-sanity / <release>-cm-pm-seed. (954ee5f)
• Minor edit to just stimulate helm publish. (64fa696)
• G2P-5222 Freeze GitHub repo: add "moved to GitLab" README notice and disable auto build/publish (remove push/tag triggers). (d826db5)
• G2P-5335 Re-run GitLab pipeline with fixed chart job (51fd07c)
• G2P-5348 Minor edit of README. (58f81a4)
• G2P-5335 Minor edit of README. (f87a6ea)
• G2P-5348 Moved repo from Github as is. (8bf5787)
• G2P-5335 Grant packages: write in caller to satisfy reusable workflow (fix startup failure) (88041e0)
• G2P-5335 Publish consent-manager images and chart to GitLab; drop GHCR (b38f1e7)
• G2P-5335 consent-manager: publish images + chart to GHCR (chart under charts/ to avoid image name clash) (b736910)
• G2P-5335 Publish images + chart to GHCR only (OCI), values to ghcr.io (6f7508a)
• G2P-5335 clarify changelog workflow_dispatch input descriptions (326edee)
• G2P-5335 forward changelog dispatch inputs to central workflow (75b649f)
• G2P-5335 Fix in publish. (9ff69b6)
• G2P-5335 ci: replace docker-build + helm-publish with central build-publish workflow (0a508a6)

What's shown here. This catalogue lists every stable release, plus the latest 20 develop builds and the latest 10 release candidates per release line -- candidates are KEPT after their release ships, as the audit trail of the release run. Older develop builds and release candidates are pruned as they are superseded. Those versions still exist in the container and Helm registries — they are simply not listed here. This page is generated automatically from commit history; do not edit it by hand.