Verisign certificate response fails with Error 9508 -empty/invalid fields

[asif_rahmetulla]

We are trying to generate a trial 14-day Certificate Response file from Verisign. It fails with error "Error 9508 - Certificate Signing Request contains empty field(s)" when supplied with the certificate request. We have made several attempts to through transaction STRUST and via sapgenpse command to create certificate request file with unique DN which has values for CN, OU, O, ST, L, C. But no success.

Has anyone successfully created a CSR from verisign for enable SSL in NW2004s?

Thanks,

Asif

[Former Member]

Hi Asif,

Check whether you have provided correct location/state name.

-Pinkle

[asif_rahmetulla]

Hello Pinkle,

Thanks for your response. I am specifying "Texas" which is a valid state name. For location I am using "Plano".

Am I providing incorrect information? or parameter name?

-Asif

[WolfgangJanzen]

Looks like [SAP Note 511919|https://service.sap.com/sap/support/notes/511919] could help you ...

Notice: the printable notation of the OIDs (such as "CN", "OU", ...) is not standardized.

In particular: "ST" (Street / State) -> "SP" (State-or-Province).

Cheers, Wolfgang

[asif_rahmetulla]

Hello Wolfgang,

Now it is importing the response file into STRUST. I have the Verisign Trial CA Root, Trial intermediate and the CA issued CSR (Certificate Signing Response) files. I have tried to follow OSS note 508307 to apply the certificate response but it fails with message "CA certificate missing in database". I have tried to import the certificate trial CA Root into database and then tried to import the trial intermediate and CSR together and getting error message "Cannot import certificate response".

Please share your expertise.

Thanks,

Asif

[Former Member]

Have you tried putting all in one file and them import CSR?

-

---

BEGIN CERTIFICATE-----

<Base64-coded contents of the re-issued certificate>

-

---

END CERTIFICATE-----

-

---

BEGIN CERTIFICATE-----

<Base64-coded contents of the certificate of the intermediate CA>

-

---

END CERTIFICATE-----

-

---

BEGIN CERTIFICATE-----

< Base64-coded contents of the certificate of the root CA>

-

---

END CERTIFICATE-----

If yes, then try putting each cert in individual file and save it as .crt format to check all certs are ok and valid.

-Pinkle

[Former Member]

You can also use a p7b file which contains the whole certification chain and imports easlily in STRUST.

Regards,

Olivier

[asif_rahmetulla]

Thanks!