v6.0.0

What's Changed

Replace domainNameFromBidRequest with domainOrAppNameFromBidRequest for both Bidstream client and UID2 client. Additionally, within the DecryptionStatus class, modify DomainNameCheckFailed to DomainOrAppNameCheckFailed.

Full Changelog: v5.6.22...v6.0.0

v5.6.22

What's Changed

• The UID2Client class has been deprecated and is replaced by BidstreamClient (for DSPs) and SharingClient (for sharers).
• The new BidstreamClient class ensures long-lived tokens, such as Sharing tokens, are rejected.
• Additionally, the BidstreamClient and the SharingClient class
  • reject tokens with invalid timestamps.
  • have a reduced interface that's specific to their use-case (in contrast to the deprecated UID2Client).
• Token expiry time is now available in the decryption response
• Usage examples are shown here: https://unifiedid.com/docs/sdks/uid2-sdk-ref-csharp-dotnet

Full Changelog: v5.4.24...v5.6.22

v5.4.24

📦 Uncategorized

• UID2-2921 Fix C# SDK readme to point to unifiedid.com instead - ( PR: #39 )
• Rename pipeline job name - ( PR: #40 )
• UID2-2329 Pass in vulnerability_failure_severity - ( PR: #41 )

NuGet

<dependency>
    <groupId>com.uid2</groupId>
    <artifactId>uid2-client-net</artifactId>
    <version>5.4.24</version>
</dependency>

Nuget Files

• UID2.Client.5.4.24.nupkg

Changelog

• UID2-2921 Fix C# SDK readme to point to unifiedid.com instead - ( PR: #39 )
• Rename pipeline job name - ( PR: #40 )
• UID2-2329 Pass in vulnerability_failure_severity - ( PR: #41 )

v5.4.16

📦 Uncategorized

• [CI Pipeline] Released Patch version: 5.4.16 - ( PR: #38 )

NuGet

<dependency>
    <groupId>com.uid2</groupId>
    <artifactId>uid2-client-net</artifactId>
    <version>5.4.16</version>
</dependency>

Nuget Files

• UID2.Client.5.4.16.nupkg

Changelog

• [CI Pipeline] Released Patch version: 5.4.16 - ( PR: #38 )

What's Changed

• [CI Pipeline] Released Patch version: 5.4.16 by @github-actions in #38

Full Changelog: v5.4.14...v5.4.16

v5.4.0

What's Changed

• Added v3/v4 identity type and advertising token version fields in DecryptionResponse by @gmsdelmundo in #21

Full Changelog: v5.3.2...v5.4.0

v5.3.2

What's Changed

• Fix to return an error when UID2 token input is <4 chars by @sunnywu in #25

Full Changelog: v5.3.1...v5.3.2

v5.3.1

What's Changed

• Allows DecryptionResponse Decrypt(string token) or DecryptionResponse Decrypt(string token, DateTime utcNow) methods not to do domain name check in case DSPdoesn't want to enable domain name check for CSTG-derived tokens by @sunnywu in #23

Full Changelog: v5.3.0...v5.3.1

v5.3.0

What's Changed

• Added DecryptionResponse.IsClientSideGenerated for decrypting tokens generated from Client Side Token Generation way. They are usually filled but can be null if the token decryption fails and we cannot determine the property.
• Added DecryptionStatus.UserOptedOut when a Client Side Token Generated token is decrypted and it indicates the user actually has opted out previously so no valid raw UID2 can be used after this decrypt call.
• Created a second/optional method interface "DecryptionResponse Decrypt(string token, string expectedDomainName)" for domain name check when decrypting UID2 token, to verify if the expectedDomainName param belongs to the UID2 creator's allowed domain name list (which needs to be registered with UID2 admins). If they don't match then it's a domain name check failure.
• new DecryptionStatus.DomainNameCheckFailed status to indicate if domain name check failed
• Refactored encryption tests to use a builder for advertiser token