topic Re: Start Before Logon XML Not Taking in Network Security

Start Before Logon XML Not Taking

benharned — Fri, 21 Feb 2020 11:37:36 GMT

Following the steps in:

http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00809f0d75.shtml#svg to configure SBL (ASDM), when I try to assign the XML profile to the group policy (step 11), I hit OK after choosing the XML file and it doesn't take. Just comes back with the "Add SSL VPN Client Profiles" dialog.

I used the XML file provided with the AnyConnect client and just changed the host settings, so the syntax should be right.

Any other suggestions?

Re: Start Before Logon XML Not Taking

Robert Salazar — Wed, 12 Aug 2009 18:11:31 GMT

You can validate the the xml schema at this site:

http://tools.decisionsoft.com/schemaValidate/

Re: Start Before Logon XML Not Taking

benharned — Wed, 12 Aug 2009 18:18:24 GMT

Thanks for the link. Ran it, all good.

Well formed: VALID

Schema validation: VALID

Now what? Is there a setting somewhere I missed? I followed the instructions.

Re: Start Before Logon XML Not Taking

Robert Salazar — Wed, 12 Aug 2009 18:24:10 GMT

what version of ASA and asdm are u using?

what happens if you use cli instead?

Re: Start Before Logon XML Not Taking

benharned — Wed, 12 Aug 2009 18:32:17 GMT

ASA 8.2(1)

ASDM 6.2(1)

I'm not the most versed in CLI so I am not totally sure of the right commands. When I followed the examples in the guide, I kept getting an invalid error in step 3 "svc profiles NAME disk0:/..." The indicator was showing under the NAME.

Re: Start Before Logon XML Not Taking

benharned — Mon, 17 Aug 2009 20:50:53 GMT

Anyone? Anything?

Bump.

Re: Start Before Logon XML Not Taking

Christopher Ursich — Tue, 13 Jul 2010 23:00:12 GMT

+1 here. I am using ASA code 8.2(2) and ASDM 6.3(1). When editing the group policy, in the "SSL VPN Client" section, I change the "Client Profile to Download" from "-- None --" to one of my client profiles and click 'OK.' The 'Apply' button does not become clickable, and when I re-open the group policy for editing, the setting is back to None.