New Releases and repositories for the swiyu Public Beta Trust Infrastructure
Some components of the swiyu Public Beta Trust Infrastructure got new releases we would like you to inform about. If you are running older versions of the generic issuer or verifier, you have to update these components immediatly. In addition, we’ve published new repositories for testing your deployments as well as credential issuance and verification flows.
New Versions for Android and iOS Wallets
With the latest versions Android v1.13.1 and iOS v1.14.0 we’ve fixed some issues that have been raised by the community:
- Android: Do not overwrite claims when parsing jwt
- Android: Implement Whitelist for supported Hash Algorithms
- iOS: Enforce “isBetaIssuer” check
With the next wallet releases, we’ll proceed the contract-step for the issues Access-Token-Request uses wrong Content-Type respectively Wallet sends token endpoint params as query params.
Generic Issuer Version 2.4.2
- Contract step for Token endpoint expected x-www-form-urlencoded
- Contract change: Removed c_nonce from OAuthTokenDto the nonce can be retrieved from the nonce endpoint. The nonce column from credential_offer table is also removed.
- Feature: Signed Issuer Metadata
- Fixed: Issue, when content length not set
- Fixed: Possibly invalid credentials on bad usage
- A lot of new endpoints, fixes, and changes - please refer to the changelog
Generic Verifier Version 2.3.1
- Breaking change introduced with version 2.2.0: Either accepted_issuer_dids or trust_anchors must contain a value. The list itself cannot be empty, as this would implicate that nothing is trusted. This is to improve security by avoiding misconfigurations that would lead to accepting any issuer.
- Status list resolving does no longer accept http urls for status lists. Only https urls are allowed now.
- Feature: Payload encryption during verification flow
- Fix: “Split” function removes empty strings
- Fix: Bad error handling if vp_formats is missing in verifier_metadata
- Several changes and fixes - for the complete overview, please refer to the changelog
DID Toolbox Version 1.9.0
- Feature: The DID Toolbox Java API enhanced - supplying verification material for verification methods (of a DID Document) unambiguously (no default values) using new and more potent fluent methods
assertionMethods/authentications(forDidLog[Creator\|Updater]Contextclasses). Deprecations introduced accordingly. - Feature: Changed Proof-of-Possession (PoP) creation to include a resolvable
kidin the JWT header.
DID Resolver Version 2.6.0
- Fix: Potential problems in “replaceAll”
- Feature: Further UniFFI language bindings added
New Repositories for a better test coverage
To better support the implementation of our generic components and the validation of your own deployments we’ve released two new repositories. We hope these are helpful to our community and we look forward to hearing your feedback.
Generic Application Test
The Generic Application Test is a test system designed to run end-to-end (E2E) tests against the generic swiyu Issuer and Verifier components. Its primary goal is to validate the generic behavior of these components in isolation, without relying on a full trust infrastructure or real wallets. The system focuses on testing the issuance and verification flows, independently of any specific ecosystem or deployment.
Test Wallet
The swiyu Generic Test Wallet is a web application that simulates a wallet to test credential issuance and verification flows based on OIDC4VCI and OIDC4VP. It is primarily intended to validate your own deployment of the swiyu Generic Issuer and Verifier components.