Releases: procivis/one-wallet
Release v1.71.1
Updated compatibility with one-core v1.71.0.
For complete details, see the full release notes.
Breaking changes
- WAA → WIA terminology
⚠️ - "Wallet app attestation" renamed to "wallet instance attestation" per EU ARF
- API parameters renamed:
requiresAppAttestation→requiresWalletInstanceAttestation,walletAppAttestation→walletInstanceAttestation - Update wallet integrations accordingly
Other Procivis One updates
- Access Certificates - Issue Access Certificates for wallet-relying parties in EU National Registries
- OID4VP in Organizational Wallet - Accept proof requests with credential sets
- Transaction codes - One-time codes for OpenID4VCI issuance flows
- Schema ID improvements - Optional schema IDs for ISO mdoc and SD-JWT VC formats
Release v1.70.0
Updated compatibility with one-core v1.70.0.
For complete details, see the full release notes.
Other Procivis One updates
- Certificate Authorities - Create CA identifiers with support for CSRs, importing CA chains, creating self-signed root CAs, and signing X.509 certificates
- Optional revocation methods - Revocation method selection now optional during credential schema creation
- Registration Certificate APIs - Updated APIs for issuing Registration Certificates to wallet-relying parties
- Desk UI improvements - Copy schemas between organizations, improved country profile visibility, and customizable list filters
Release v1.69.1
Updated compatibility with one-core v1.69.1.
For complete details, see the full release notes.
Other Procivis One updates
- Issue Registration Certificates - Issue Registration Certificates to wallet-relying parties
- National Register - Public API - Wallet-Relying Party Registry service includes new public GET endpoint
- Simplified deployment - Updated Quick Start with streamlined full stack deployment
- Desk UI improvements - Enhanced proof schema creation workflow
Release v1.68.1
Updated compatibility with one-core v1.68.0.
For complete details, see the full release notes.
- Bug fixes and minor improvements
Other Procivis One updates
- Signature endpoints - New
/api/signatureendpoints for signing Registration Certificates (wallet-relying party registries) - System announcements in Desk - Desk UI now supports displaying system announcements
Release v1.67.1
Updated compatibility with one-core v1.67.2.
For complete details, see the full release notes.
New features
- Finnish translations - thanks to @samuelmr for the contribution!
- x509_hash client ID scheme - New client identifier scheme supported for OpenID4VP draft 25 and later
Other Procivis One updates
- Centralized history storage - Server components now store all history events centrally in Core
- Wallet-relying party registry lifecycle management - Added support for suspension, reactivation, revocation, and deletion
Release v1.66.1
What's new in v1.66.1
Updated compatibility with one-core v1.66.1.
This release includes breaking changes to OpenID4VCI URL schemes and configurable time leeways. Please review the breaking changes carefully before upgrading.
For complete details, see the full release notes.
v1.66.1 ⚠️
Breaking changes
- OpenID4VCI URL scheme standardization
⚠️ - OpenID4VCI 1.0 now uses the standard
openid-credential-offerscheme (removing-final1suffix) - Wallets no longer recognize the old
openid-credential-offer-final1scheme - Wallets now require
OPENID_METADATAcache entity configuration - See the release notes for migration guidance
- OpenID4VCI 1.0 now uses the standard
New features
- Wallet Providing (Enterprise) - New enterprise component for OpenID4VCI and ARF-compliant wallet providing with wallet attestation issuance and wallet unit revocation
- Wallet-relying party registration (Enterprise) - New enterprise component implementing ETSI TS 119 475, ETSI TS 119 411-8, and eIDAS 2.0 regulation (EU) 2025/848
v1.65.0 ⚠️
Breaking changes
- Configurable leeways
⚠️ - Time tolerance values for timestamp validation are now configurable (previously hard-coded)
- Multiple mandatory leeway configurations required across Core providers
- All values must be set in seconds with no defaults provided
- See the release notes for required configuration parameters
Release v1.64.2
What's new in v1.64.1
Updated compatibility with one-core v1.64.1.
This release includes breaking changes to credential holding workflows, new OpenID4VP 1.0 endpoints, and authentication configuration updates. Please review the breaking changes carefully before upgrading.
For complete details, see the full release notes.
v1.64.0 ⚠️
Breaking changes
- Updated credential holding workflow
⚠️ handle-invitationno longer returnscredentialIdsissuance-acceptnow required for all flows and returns thecredentialId- Credentials created after acceptance instead of before
New features
- Organization slugs - URL-friendly slugs for easier link sharing and automatic organization switching in Desk UI
- Wallet minimum version enforcement - Issuers can specify minimum Wallet App versions for attestations
v1.63.0 ⚠️
Breaking changes
-
OpenID4VP 1.0: New
/v2presentation endpoints⚠️ - Wallets using OpenID4VP 1.0 must migrate to new
/v2endpoints with DCQL support - OpenID4VP draft versions continue using
/v1endpoints unchanged
- Wallets using OpenID4VP 1.0 must migrate to new
-
Standardized list endpoint filters
⚠️ - Filter parameters renamed and converted to arrays (e.g.,
role→roles,state→states) - Update query parameters in API calls accordingly
- Filter parameters renamed and converted to arrays (e.g.,
v1.62.0 ⚠️
Breaking changes
- Authentication configuration restructured
⚠️ - Move
app.authTokentoapp.auth.staticTokenand setapp.auth.mode: STATIC
- Move
New features
- STS authentication mode - Enterprise-grade authentication with multi-tenancy and fine-grained access control
- OpenID4VCI 1.0 support - v1.0 protocol now supported alongside draft versions
- Wallet Unit Attestation enhancements - Added revocation support and organization-level attachment
Release v1.61.1
What's new in v1.61.1
Updated compatibility with one-core v1.61.3.
- Wallet Unit Attestation now supported
- Added support for Wallet Unit Attestations using the OAuth 2.0
Attestation-Based Client Authentication protocol - The Procivis One Wallet can request an attestation from
Procivis One Core - Platform-specific validation ensures wallet instances are legitimate
apps - Attestations enable wallet instances to prove app integrity to both
issuer and verifiers
- Added support for Wallet Unit Attestations using the OAuth 2.0
- NFC Engagement
- Added NFC engagement support for Android devices using the ISO 18013-5
mdoc flow - The Procivis One Wallet now supports both QR code and NFC engagement for
presentation flows on compatible devices - See the ISO offline flow for NFC
engagement configurations
- Added NFC engagement support for Android devices using the ISO 18013-5