Releases: impierce/ssi-agent
Releases · impierce/ssi-agent
v1.0.0-beta.13
1.0.0-beta.13 (2025-10-29)
Bug Fixes
- initialize database clients (#216) (243a89b)
- remove duplicate OID4VP authorization response validation (#231) (2e7763e)
- use
hostnameasdisplaydefault inproductionprofile (#228) (7061540)
Features
- add transaction code support to OID4VCI flow (#213) (7d84f08)
- expose basic HTTP API metrics (#212) (32bff21)
- migrate to OID4VP draft 28 (DCQL,
vp_token) (#201) (46aa715) - migrate to OpenID4VCI draft 15 (#217) (4a6ef0c)
- support MongoDB event store (#210) (f40c3cd)
BREAKING CHANGES
-
- OpenID4VCI flow is updated to https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-15.html. This makes UniCore incompatible with Wallets that support older draft versions
-
- New
dcql_queryreplacespresentation_definitionas the query structure in authorization requests (OID4VP draft 28).
- New
vp_tokenresponse structure has changed and is now an object where the key is the id value used for a Credential Query in thedcql_queryand the value is an array of one or more Presentations that match the respective Credential Query.- Added new validation functions to ensure
vp_tokencorresponds to requested credentials.
v1.0.0-beta.12
v1.0.0-beta.11
1.0.0-beta.11 (2025-08-13)
Features
- add
credentialStatus, serveStatus List Token(#204) (e1906df) - add support for multiple credential configurations (#193) (5832b33)
- change public
displaydata during runtime (#199) (8512590) - migrate to IOTA Rebased (#205) (c0ca611)
BREAKING CHANGES
- Schema updates to the
Documentaggregates now prevent UniCore from loading state from event stores created with previous versions. Since data migrations are not supported yet, a fresh database is required. - When utilizing the JIT Credential flow, the
/v0/offersendpoint now requires thecredentialConfigurationIdsfield which should contain all the IDs of the Credential Configurations corresponding to the JIT Credential(s) to be issued. - Schema updates to the
OfferandServerConfigaggregates now prevent UniCore from loading state from event stores created with previous versions. Since data migrations are not supported yet, a fresh database is required.
v1.0.0-beta.10
1.0.0-beta.10 (2025-06-10)
Features
- add
public_url, renameurltoapplication_url(#186) (4ea5618) - add OpenID4VCI Notification Endpoint (#178) (4a1794e)
- introduce application profiles with sensible default configuration (#182) (549ccae)
- return
PublicErrorfor public Issuance endpoints (#190) (eba534e)
BREAKING CHANGES
-
- Removed
UNICORE__PORTandUNICORE__BASE_PATHenvironment variables. Their functionality is now covered byUNICORE__APPLICATION_URL, which can include port and base path components as needed for internal use.
Note: Please review your deployment and configuration files to ensure compatibility with these changes.
- Removed
v1.0.0-beta.9
1.0.0-beta.9 (2025-03-24)
Features
- add
/versionand/infometadata endpoints (#158) (2770ac2) - add Domain Linkage for
did:iotaDID Method (#160) (5f55caa) - add endpoints to list and retrieve DID Documents (#171) (3840147)
- add Problem Details for Issuance and Persistence HTTP API errors (#175) (96f25ac)
- remove ˋdid:iota:rmsˋ DID method (discontinued) (#168) (938c236)
- use
credential_offer_uriby default during credential issuance (#166) (306912a)
BREAKING CHANGES
- Schema updates to the
DocumentandServiceaggregates now prevent UniCore from loading state from event stores created with previous versions. Since data migrations are not supported yet, a fresh database is required. - The following environment variables have been deprecated:
UNICORE__DID_DOCUMENT_CACHE__ENABLEDUNICORE__DID_DOCUMENT_CACHE__TTLUNICORE__DID_DOCUMENT_CACHE__INCLUDE
- The
did:iota:rmsDID Method has been deprecated - The following environment variables have been deprecated:
UNICORE__SECRET_MANAGER__ISSUER_DIDUNICORE__SECRET_MANAGER__ISSUER_FRAGMENT
v1.0.0-beta.8
1.0.0-beta.8 (2024-12-13)
Bug Fixes
Features
- implement liveness probe at
/healthz(#152) (98045e9) - require credential expiration date, use credential
idin JWT (#150) (65c9653) - upload holder credentials via HTTP API (#141) (8c8c246)
BREAKING CHANGES
- require
expiresAtproperty when creating a credential via the HTTP API
The expiresAt field is now required when creating a credential on /v0/credentials. Accepted values are ISO 8601 timestamps (UTC) such as 2024-12-09T16:51:29Z or the value "never".
Migration guide
- supply
expiresAtfor each request to/v0/credentials
v1.0.0-beta.7
v1.0.0-beta.6
1.0.0-beta.6 (2024-12-03)
Features
BREAKING CHANGES
- return collection as an array of objects instead of a map
- rename primary identifier
The response types for the following endpoints have been changed from a map of objects to an array of objects:
/v0/holder/credentials/v0/holder/offers/v0/holder/presentations/v0/connections/v0/services/v0/credentials/v0/offers
Before
{
{
"credential_id": "bf766ebe-0a52-4531-ac24-88af1b854b55"
...
}
}
After
[
{
"id": "bf766ebe-0a52-4531-ac24-88af1b854b55"
...
}
]
Migration guide
- Parse responses as lists instead of objects
- Use the generic
idproperty instead of having to search the response for the identifier