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 <jckid...@aep.com> > > 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.
