Releases: MobileID-Strong-Authentication/mobileid-client-java
v1.5.7
Release 1.5.7 changes:
-
New Req:
- SignatureValidatorImpl changes for new dtbs format as json and mimeType "application/vnd.mobileid.txn-approval"
-
Dependecies:
- Bumps com.fasterxml.jackson.core:jackson-core from 2.14.0 to 2.15.0.
- Bumps SonarSource/sonarqube-scan-action from 5.2.0 to 5.3.1.
- Bumps ch.qos.logback:logback-classic from 1.4.12 to 1.5.18
- Bumps org.bouncycastle:bcutil-jdk18on to 1.78.1
-
Bug fixes:
- Typo in countryBlackList (#19)
-
Thanks for contribution:
v1.5.6
v1.5.5
Add support for sslContext configuration for mid-java-client-rest via sslContext property in TlsConfiguration instance.
Introduced "geofencing" parameter to be used with SignatureRequest via cli. The change ensures geofencing data is returned
only when the geofencing parameter in the cli is explicitly set.
Introduced get-mid-sn query/param for cli interface to retrieve Mobile ID serial number, exposed getMIDSerialNumber method
via SignatureValidator interface for programmatically retrieving mentioned property.
v1.5.4
v1.5.3
v1.5.2
v1.5.1
v1.5.0
Add support for signature validation, after a mobile signature is successfully created.
Add a new component that can be configured separately for validating the signing certificate, the certificate path, the actual signature and the DTBD/DTBS that was signed.
Add support for signature validation to the CLI mode.
v1.4.0
No changes since v1.4.0-beta2.
Since 1.3.0, proxy configuration capabilities were added to the REST and SOAP protocols. Now the Mobile ID client can be configured to connect to the Mobile ID backend via an HTTP proxy, with or without Basic authentication. This works both for command line and for programmatic mode.
v1.3.0
Add optional override of AP ID and AP Password for each request and for the tracking object of a signature operation.
This helps with sending requests on behalf of various APs, instead of relying only on the common AP ID + AP password
configured in ClientConfiguration.