Releases: getyoti/yoti-java-sdk
v2.6.1
v2.6.0
Added
SourceConstraintBuilder
for use in Dynamic ScenariosAttributeIssuanceDetails
- This can be accessed through
ActivityDetails
once a share has been completed usingThirdPartyAttributeExtensionBuilder
- This can be accessed through
ThirdPartyAttributeIssuingRequest
Changed
SignedRequest
- Allow users to specify
Image
as return class type if retrieving an image from a Yoti endpoint SignedRequestResponse
can be retrieved to access the raw request response for custom parsing.
- Allow users to specify
WantedAttribute
name
property is now validated to not be null/empty, and will throw anIllegalArgumentException
if validation fails
v2.5.1
v2.5.0
v2.4.0
v2.3.0
v2.2.0
Added
- New client to support dynamic scenarios. You can now specify which attributes to request on the fly using this SDK
- New model for AgeVerification. The SDK now supports multiple age checks on a single profile/scenario
- New parentRememberMeId on ActivityDetails, to support identifying users across a single organisation
- Early inclusion of a sandbox client. As a consequence of this work, some of the DTOs now have builders, and equals and hashCode has been overriden on the following:
-- DateValue
-- DateTimeValue
-- SignedTimestampValue
-- TimeValue
Deprecated
- Profile.isAgeVerified() - please use the new AgeVerification object together with findAgeOverVerification or findAgeUnderVerification
Changed
The spring demo has been updated with a much nicer UI.
v2.1.0
Changed
We plan to replace the Attribute postal_address with an Attribute structured_postal_address.
In an effort to avoid breaking existing integrations, if the postal_address is missing the SDK will now check for the structured_postal_address and substitute it in.
Added
- All Image objects can now provide a base64 string
Deprecated
v2.0.0
Removed
Dropped support for Java 6
Minimum supported Java version is now 7.
Removed toString() methods
We've removed implementations of toString() from all the DTOs returned through the public API.
Changed
New interfaces - Attribute and Anchor
The old com.yoti.api.client.Attribute
class has been replaced with com.yoti.api.client.Attribute<T>
, which now exposes a List<Anchor>
for the sources and verifiers of the attribute.
The old Set<String> getSources()
and Set<String> getVerifiers()
methods have been replaced with List<Anchor> getSources()
and List<Anchor> getVerifiers()
.
Changes to HumanProfile and ApplicationProfile
All attributes are now returned as an instance of Attribute<T>
. Use the Attribute<T>.getValue()
method to determine the actual value of an attribute.
Consequently, all the getXXXSources
and getXXXVerifiers
methods have been removed, as well as the is(name, defaultValue)
helper method
No Enums returned by the public API
Yoti is adding new functionality all the time. To avoid the risk the new values returned to the SDK will cause it to break, the SDK will no longer try to map returned values to Enums. Each SDK release will define String constants in the public API for the possible values known at the time of release.
The two Enums removed are:
- DocumentType - the
DocumentDetails.getType()
method now returns a String. The possible values are exposed as constants on thecom.yoti.api.client.DocumentDetails
interface. - HumanProfile.Gender -
HumanProfile.getGender()
now returns anAttribute<String>
. Possible values are defined incom.yoti.api.client.HumanProfile
.