ConnectionData.xml

[MDeMarco603]

Hi,

I have a problem with my ConnectionData.xml file contents, in which it contains old PSN information. In attempts to prevent the file from containing old PSN information I placed an ACL at the L3 SVI for my clients which denys ip to old PSN servers. Thinking that if the calls from the client to the old PSN were unsuccessful, it would fail to be defined in ConnectionData.xml.

My acl is successful in is operation but ConnectionData.xml still continues to be populated with old PSN info.

Does anyone know how ConnectionData.xml is being created with it's contents?

This file is found in

C:\Users\<currentuser>\AppData\Local\Cisco\Cisco AnyConnect Secure Mobility Client\

Thanks

[kthiruve · Accepted solution]

Hi Michael,

Connectiondata.xml file has last contacted PSN information. It is not intended to be edited.

If you want the discovery to work in your network there are other methods to use such as Discovery Host. ISE 2.2 introduced a call home that can be configured in ISE.

Please see https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-22/210523-ISE-posture-style-comparison-for-pre-and.html#anc6

That speaks in detail about the posture flow pre-ISE 2.2 and post ISE 2.2.

-Krishnan

[MDeMarco603]

Understood, I've been through this document extensively and do define DH in my posture profile for clients, yet old PSN information continues to be defined in ConnectionData.xml.

Thanks for now.. I'll continue to search for answers.

[TERRY GRACE]

Did you ever find a resolution to the old PSN data being in COnnectionData.xml? I'm having the same issue and not sure where it's coming from. Old data shown along with new even after I delete the file from the client and it gets recreated on next connect.

[Sri Harsha Dasari]

You have to delete the static file entry under user profile App Data and also update the Posture Module.

Please refer the below link.

https://apronets.com/2018/02/15/ise-posture-troubleshooting/