Skip to content

Releases: OpenG2P/consent-manager

Release list

Release 1.0.3

Release 1.0.3 Latest
Latest

Choose a tag to compare

View all tags
@shibu-narayanan shibu-narayanan released this 04 Sep 11:29
1.0.3
b83b37c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

  • Bump version to 1.0.3 and update image tags to 1.0.3 by @vin0dkhichar in #7

New Contributors

Full Changelog: 1.0.2...1.0.3

Contributors

vin0dkhichar
Assets 2
Loading

Version 1.0.2 release for consent managee

Version 1.0.2 release for consent managee

Choose a tag to compare

View all tags
@shibu-narayanan shibu-narayanan released this 01 Sep 11:15
1.0.2
52bb1b0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

Full Changelog: 1.0.1...1.0.2

Contributors

mkumar-02
Loading

1.0.1 version release for consent-manager

1.0.1 version release for consent-manager

Choose a tag to compare

View all tags
@shibu-narayanan shibu-narayanan released this 01 Sep 09:38
1.0.1
c84a6dd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Updated

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

First release for consent manager

First release for consent manager

Choose a tag to compare

View all tags
@shibu-narayanan shibu-narayanan released this 01 Sep 09:18
1.0.0
c67030b

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

Loading