topic Re: Problems uploading webauthcert to mobility express controller in Wireless

Problems uploading webauthcert to mobility express controller

unaiabrisketa — Mon, 07 Feb 2022 13:26:58 GMT

Hi,

I have a mobility express controller in the 8.10 firmware version. I am trying to upload the certificate using the cli after following the defined proccess for getting the encoded pem file.

I have been able to do it in a 8.0 version wireless controller. So the certificate seems to be correct.

Troublehsooting the proccess in the aironet espress controller I get the follwing errors:

TFTP receive complete... Installing Certificate.
*TransferTask: Nov 13 01:48:16.557: RESULT_CODE:13

*TransferTask: Nov 13 01:48:20.557: Adding cert (9165 bytes) with certificate key password.

*TransferTask: Nov 13 01:48:20.557: Add WebAuth Cert: Adding certificate & private key using password 1234
*TransferTask: Nov 13 01:48:20.557: Add ID Cert: Adding certificate & private key using password 1234
*TransferTask: Nov 13 01:48:20.557: Add Cert to ID Table: Adding certificate (name: bsnSslWebauthCert) to ID table using password 1234
*TransferTask: Nov 13 01:48:20.557: Add Cert to ID Table: Decoding PEM-encoded Certificate (verify: YES)
*TransferTask: Nov 13 01:48:20.557: Decode & Verify PEM Cert: Cert/Key Length was 0, so taking string length instead
*TransferTask: Nov 13 01:48:20.557: Decode & Verify PEM Cert: Cert/Key Length 9165 & VERIFY
*TransferTask: Nov 13 01:48:20.568: Decode & Verify PEM Cert: X509 Cert Verification return code: 0
*TransferTask: Nov 13 01:48:20.568: Decode & Verify PEM Cert: X509 Cert Verification result text: certificate is not yet valid
*TransferTask: Nov 13 01:48:20.568: Decode & Verify PEM Cert: Error in X509 Cert Verification at 0 depth: certificate is not yet valid
*TransferTask: Nov 13 01:48:20.569: Add Cert to ID Table: Error decoding (verify: YES) PEM certificate
*TransferTask: Nov 13 01:48:20.569: Add ID Cert: Error decoding / adding cert to ID cert table (verifyChain: TRUE)
*TransferTask: Nov 13 01:48:20.569: Add WebAuth Cert: Error adding ID cert
*TransferTask: Nov 13 01:48:20.569: RESULT_STRING: Error installing certificate.

*TransferTask: Nov 13 01:48:20.569: RESULT_CODE:12

Error installing certificate.

I have searched for a while but I didn't find the same issue in other topics. Cooul anybody help me?

Thanks!

Re: Problems uploading webauthcert to mobility express controller

jagan.chowdam — Mon, 07 Feb 2022 14:10:14 GMT

Both controllers have the same time setup?

From the error log "X509 Cert Verification result text: certificate is not yet valid".

Verify the valid from date and time on the certificate

/** Please rate useful responses **/

Re: Problems uploading webauthcert to mobility express controller

Scott Fella — Mon, 07 Feb 2022 15:59:38 GMT

My suggestion is to post the link of the guide you followed. With certificates, it also depends on how you generate the CSR and what tool and version you used. v8.0 is old and many things have changed between that version and v8.10. So this doesn't surprise me that it works with one and not the other.

Re: Problems uploading webauthcert to mobility express controller

Prince.O — Mon, 07 Feb 2022 19:45:28 GMT

Hi,

As @jagan.chowdam stated, it looks like your controller having issues is showing the wrong date & time as " Nov 13 01:48:20.569 " and thus the cert is showing as not yet valid in the logs.

Please validate the time on the controller and if necessary, set this to the correct time and try uploading the cert again

Re: Problems uploading webauthcert to mobility express controller

Rich R — Tue, 08 Feb 2022 15:30:17 GMT

Can you show the EXACT commands you used to update the cert?

Enable these debugs before running the commands and capture the debug logs:

debug transfer all enable

debug pm pki enable

Afterwards disable debug with "debug disable-all".

We use the same cert across 8.0, 8.5 and 8.10 WLCs (CSR generated using OpenSSL)

The error message about "not yet valid" is misleading - almost anything that causes the cert update to fail can result in that error message - including incorrect password.