>If your string looks like a longer version of this then it will be from a .PEM file:
-----BEGIN CERTIFICATE-----
>MIIDXDCCAsWgAwIBAgIBADANBgkqhkiG9w0BAQQFADCBgTELMAkGA1UEBhMCR0Ix
>DzANBgNVBAgTBkRlcmJ5czEVMBMGA1UEBxMMQ2hlc3RlcmZpZWxkMRUwEwYDVQQK
>CSqGSIb3DQEBBAUAA4GBAAjRRpNbEhxjpewJDe5zKZ0tVoQvcLaqrWNYFHBmrcJp
>HuxB7sah8FIGP5Qyko8TS0cpwrCsh3e47Rw2R+SzThnm8mP1KHKo2G6XAaOelvth
>DMdl9gHXU+qzR2BIQV2e+Zsl7lmjCx8qDSVP34qbQFKAtImoTn3H/mqTt35pwJc/
>-----END CERTIFICATE-----
in which case my suggestion will work (although you will need to strip the BEGIN CERTIFICATE / END CERTIFICATE lines if they are present before using ConvertFromBase64()
The string does not contain the start and end markers. Its total bytes is 2452. This divides at 38.31 So, it is not a based 64. Also, there is no alignment. If their is no wrap, the string is all in one line. If there is a wrap, it wraps at the + sign. This is a custom certificate. The receiver processes the authentication of this certificate manually. They haven't told us how to send it. However, it is not at the method level as the method only accept one parameter, which is a XML. So, the only way to send the certificate is based on what I thought. However, if this is not a real certificate or not a base 64 certificate, I wonder if that will work.
