Controller-less WLANs

 View Only
last person joined: one year ago 

Articles relating to existing and legacy HPE Aruba Networking products and solutions including IAP, Central / HPE Aruba Networking Central, MSR, and Outdoor Mesh

IAP fails to connect to Activate server & shows the error "ASN no signer error to confirm failure" 

May 16, 2018 07:25 AM

Q:

IAP fails to connect to Activate server & shows the error "ASN no signer error to confirm failure"



A:

In this case, IAP is already configured  for the following :

  1. It can resolve/ping activate server.
  2. Clock is set up correctly.
  3. There is no firewall present on the network that is blocking the traffic between IAP & activate server.

However, when we check the ap-debug logs, we would see the following message:

show log ap-debug | include awc

awc[4028]: Failed to establish SSL connection: Error code is -1:ASN no signer error to confirm failure  

Explanation for the above error:

When IAP is trying to negotiate the SSL connection,it is unable to verify the activate server certificate.IAP does not have corresponding CA cert which would help it in validating the certificate presented by activate server.

This should ideally not happen as IAP-Activate SSL negotiation is based off factory certificates. Please report such issues to TAC team for further analysis.
 

Statistics
0 Favorited
9 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.