SecureClient certificate authentication problem

[MarcinBartnik6325]

Hi all,

Just downloaded SecureClient 5.1.17.3394 and I am having trubles with authentication with certificate after upgrade.

After downgrade to previous version I used so far 5.1.16.194 the problem disappeares.

The 5.1.17.3394 client getting me message that "No valid certificate to authenticate"

Forget to mention that I am working on Windows OS.

Doeas anybody having this issue as well? What can I do to debug this problem. This is probably bug in SecureClient because many  previous versions worked perfectly.

Thanks.

[MarcinBartnik6325]

I found a workaroud.

We have a Certificate Matching statemt in profile file on ASA headend. Seems that the new version have a problem with proper identification of that information. After delete this:

<TemplateIdentifier>

<TemplateIdentifierDefinition Operator="Include">

1.3.6.1.4.1.311.21.8

</TemplateIdentifierDefinition>

</TemplateIdentifier>

from XML file connection is able to establish and authenticate using certificate.

This is probably a BUG.

Also after removing this from profile configuration on ASA connection works again.

[Daniel G.]

Today I downloaded the same version of Secure Client and had to remove it immediately for the same reason.
I tried different options — changing the operator (equal/include), using the template name — but nothing works.
In my opinion, this looks like a bug.
I’m just not sure how to report it — probably only via TAC?

[stsargen]

Please see https://bst.cisco.com/quickview/bug/CSCwu49863.  I think that is the issue you are hitting.