Problem with WebVPN and Javascript

Unanswered Question
Jun 17th, 2008

I am trying to get the WebVPN working with one of our applications hosted in house and the parsing/modifying of the javascript is wrong. Just wondering if anyone else has come across this or if there is a workaround or something like that. Example below.

Original Line of code

setTimeout((function() {this.respondToReadyState(1)}).bind(this), 10);

WebVPN replacement

setTimeout(webvpn_mangle_eval((function()){this.respondToReadyState(1)}).bind(this), 10);

As you can see the it puts the brackets for the call webvpn_mangle_eval in the wrong place. It look like the inline function in the line of code is messing it up.

Any ideas would be great.


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
colindjackman Thu, 06/19/2008 - 03:46

Neither - we use a cluster of VPN 3030 appliances, firmware revision

"VPN 3000 Concentrator Version 4.7.2.O Mar 05 2008 16:24:28".



reed.savory Tue, 06/24/2008 - 09:52

I'm working with the original poster on this issue.

The VPN 3000 concentrators do in fact apparently rewrite JAVA, although it isn't a function that can be adjusted in terms of how it happens - there doesn't appear to be any administrative settings that would allow you to control how it does it, other than disabling JAVA entirely.

There's a mention in the release notes of the most recent firmware release (which we're running) that indicates an issue being fixed with an application called "TeamCenter" in that the concentrator was apparently causing an issue for this application in terms of how it was rewriting the JAVA code.

We in fact upgraded to the most recent firmware based on this note about fixing the writing so that it no longer impacted "TeamCenter", hoping that it might solve our issue as well, but no luck - same issue still occurs.

Farrukh Haroon Wed, 06/25/2008 - 05:46

You best option is to open a Case with Cisco TAC. There is a WEBVPN capture tool, take a capture using that and send it to TAC.

The ASA is much more flexible in this regard (Smart Tunnel, APCF etc.)



reed.savory Wed, 06/25/2008 - 05:49

For anyone else who encounters this: I opened a case with TAC.

The problem is a known bug, which I'm informed will not be fixed, since the VPN 3000 has an end-of-life schedule at this point.


This Discussion