I'm hoping you simply missed my point. The data presented is not a binary encoded certificate. base64 encoded ASCII is not binary data. userCertificate requires a binary encoded x.509 certificate.
-Jon C. Kidder American Electric Power Middleware Services 614-716-4970 Erwann Abalea <[email protected]> Sent by: [email protected] 02/07/2013 10:06 AM To [email protected] cc [email protected], [email protected], Алексей <[email protected]> Subject Re: import Certificate to userCertificate I disagree here. Decoding the Base64 presented shows the start of a certificate. It looks like it's a v3 certificate, with a serialNumber equal to 0x40000000d1bdcd0d49bf664c00ce8524, but the hashalg is something private (OID 1.3.6.1.4.1.3670.1.2), which is owned by Mr Pavlov Roman. We also have the very start of the issuerName. 2013/2/7 <[email protected]> This is not a correctly encoded certificate. The data you're trying to add to userCertificate appears to be base64 encoded ASCII and not binary. -- Erwann.
