---
title: Changelog
description: .NET Integration Kit 2.5.4 – March 2020
component: net
page_id: net:release_notes:pf_net_ik_changelog
canonical_url: https://docs.pingidentity.com/integrations/net/release_notes/pf_net_ik_changelog.html
revdate: June 20, 2024
---

# Changelog

**.NET Integration Kit 2.5.4 – March 2020**

* Added support for the SameSite cookie flag in web browsers.

**.NET Integration Kit 2.5.3 – September 2019**

* Updated the included OpenToken Adapter to version 2.5.8.

* Updated the included OpenToken Agent to version 2.5.3.

* Improved the way token timestamps are handled.

**.NET Integration Kit 2.5.2 – January 2016**

* Updated sample application data archive.

* Updated OpenToken Adapter to version 2.5.7.

**.NET Integration Kit 2.5.1 – December 2012**

* Updated to address security issue found since the previous release

* Added support for OpenToken 2.5.1 Adapter and the OpenToken 2.5.1 Agent

**.NET Integration Kit 2.5 – June 2012**

* Added support for the Microsoft .NET Framework 4.0

* Added support for 64-bit CPUs

* Removed support of the Microsoft .NET Framework 2.0

**.NET Integration Kit 2.4 – March 2010**

* Added token Replay Prevention to the OpenToken IdP Adapter Advanced Settings

**.NET Integration Kit 2.3 – November 2008**

* Added POST Transport Method for OpenToken when used by a Service Provider

* Added configuration to specify session cookie vs. persistent cookie

* Added option to set the "`Secure`" attribute on an OpenToken when cookie is used

* Added ability to bypass password obfuscation and strength enforcement for backward compatibility with previous .NET OpenToken agents

* Correctly handles `null` parameters for SOAP SLO

* Empty query string (`?`) is not automatically appended to the URL when redirecting to TargetResource

* TargetResource URL is URL encoded

* Corrected `not-before tolerance processing`

**.NET Integration Kit 2.2 – June 2008**

* Added support for SAML 2.0 `isPassive` and `ForceAuthn`

* Enforced UTF-8 encoding within OpenToken

* Symmetric key in the OpenToken agent configuration file is encrypted

* Combined the OpenToken adapter and OpenToken Java library jar files into a single adapter file for easier deployment to PingFederate

**.NET Integration Kit 2.1 – April 2008**

* Added `AgentConfiguration` class to simplify Agent instantiation

* Added Agent Toolkit API HTML Help file

**.NET Integration Kit 2.0 – December 2007**

Modified to use an open-standard, secure token called OpenToken to pass user information between an application and PingFederate. The OpenToken is passed through the user's browser as a URL query parameter or an HTTP cookie. The data within the OpenToken is a set of key/value pairs, and the data is encrypted using common encryption algorithms.

**.NET Integration Kit 1.2.1 – August 2007**

* Fixed buffer overflow issue in OpenToken Agent to allow dynamic buffer size for reading `PFTOKEN`

* OpenToken Agent `extractFromRequest` method corrected to only delete cookie if the `PFTOKEN` transport is cookie

* OpenToken Agent no longer writes messages to the Windows Event Log

* Modified to allow backward compatibility of the Standard Adapter 1.2.1 with PingFederate 4.0

* Bundled .NET sample application with distribution

**.NET Integration Kit 1.2 – May 2007**

* Added an option to encode `PFTOKEN` for handling special characters

* Added an additional constructor to allow `PFTOKEN` to use default properties for all configuration options except password, holder name, and max age

* Added `PFTOKEN` time stamp information in the log file