All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Removed support for Context Broker.
- Now the application is using database connection for data storage.
- Changed request-credential endpoint to route requests dynamically between EBSI and common workflows based on the credential offer URI.
- Rename request object to "CredentialOfferRequest".
- Add a timeout property for pin code
- Create staging profile
- Update credential contract
- Fix url in CORS
- CORS configured internally in the application
- Change way to get the cors allowed origin urls
- Update production cors to allow:
- Support for different html response codes in attestation
- LEARCredentialEmployee adapted to W3C DATA MODEL v2.0
- Delete Relying Party validation on OID4VP flow.
- Data models for new cases in credential response
- Data models for new cases in credential response
- Support for immediate(sync) issuance for DOME
- Added sending of the signed VP using the ES256
- Custom logic for the DOME verifier removed
v1.2.0 - 2024-05-22
- Feature for requesting the Signed Credential described in the OIDC4VCI DOME Profile Deferred Flow - 8 February 2024.
- Implement lifecycle status management for the credentials based on EUDI DOC ARF v1.3.0.
- Enable automatic update for dependencies.
- Enable Spring security against to authorization server
- New Context Broker entities model.
v1.1.3 - 2024-04-25
- Added WebClient bean
- Modify post-request in the process of sending the authorization response during the standard presentation flow
v1.1.2 - 2024-04-04
- Change the return value from an exception to an empty list when the user doesn't have any credentials.
- Added the logic for selecting the credential that is wanted to be presented during the DOME presentation flow.
v1.1.1 - 2024-04-02
- Change the versioning of the api endpoints from v2 to v1
- Change hardcoded verifiable presentation expiration to dynamic variable
v1.1.0 - 2024-3-26
- Support Verifiable Credentials in cwt format
- Introduced the authentication process for Verifiable Presentations flow [OpenID.VP] combined with the Self-Issued OP v2 specification [OpenID.SIOP2]
- Introduced the Verifiable Presentation flow for CWT (Cbor web token) format
- Introduced the abstraction of the configuration and the vault
- Compatibility with the attestation exchange of the DOME marketplace.
v1.0.0 - 2024-2-19
- Implemented key pair generation using the secp256r1 algorithm.
- Generate did:key identifier from ES256 key algorithm.
- Generate did:key:jwk_jcs-pub identifier from ES256 key algorithm.
- Support Scorpio Context Broker (v.4.1.14).
- Support Orion-LD.
- Support Hashicorp Vault.
- Support AZ Key Vault.
- Introduced EBSI-compliant flows for issuing and presenting digital credentials.
- Developed functionalities for QR content interpretation and credential offer management.
- Enabled the ability to interpret presentation submission filters for credential verification against user criteria.
- Creational Patterns, utilization of the Builder pattern.
- Structural Patterns, implementation of the Facade pattern.
- Factory and Adapter Patterns: Current use of the Factory pattern combined with the Adapter pattern, enhancing the flexibility and reusability of object creation and interaction within the system.
- Type Interpretation in Presentation Definition Filters: Added the ability to interpret the type of Verifiable Credential in Presentation Definition filters, allowing for more precise selection and verification of the credentials presented by the user. This enhancement facilitates adaptation to various use cases where verifying the specific type of the user's verifiable credential is required.