ADS using SSL

[Former Member]

Our aim is to send invoices from SAP in PDF format to our clients. Our development system(HSD) is only using an ABAP stack and is running on ERP 6.0 EHP4. Our Development Portal server(POD) is running an ABAP + JAVA stack, using NW 2007 SP18 & Java 7.00 SP18. ADS on the JAVA stack has been updated to: 7.00 21.3. The ADS connection is from HSD (ABAP) to POD(JAVA). I got ADS to work without a problem using basic authentication. However when trying to implement SSL, I experience the following problems. The RFC Destination to ADS works fine and I set the settings to use client certificates. The client certicates seem to be working fine, if I look @ the traces. If I try the following check : FP_CHECK_DESTINATION_SERVICE, it prompts me for a username & password. After trying 3 times I get a SOAP error. If I do the following check: https://<server>:<port>/AdobeDocumentServices/Config - I get the following result for VersionInfo: 800.20100208125913.619864 without a problem. If I use ICM and set the trace level to 3, I get the following information:

[Thr 2314] -

---

[Thr 2314] 700000001bdf3d0 000000 48545450 2f312e31 20343031 20556e61 |HTTP/1.1 401 Una|

[Thr 2314] 700000001bdf3e0 000016 7574686f 72697a65 640d0a43 6f6e6e65 |uthorized..Conne|

[Thr 2314] 700000001bdf3f0 000032 6374696f 6e3a2063 6c6f7365 0d0a5072 |ction: close..Pr|

[Thr 2314] 700000001bdf400 000048 61676d61 3a206e6f 2d636163 68650d0a |agma: no-cache..|

[Thr 2314] 700000001bdf410 000064 43616368 652d436f 6e74726f 6c3a206e |Cache-Control: n|

[Thr 2314] 700000001bdf420 000080 6f2d6361 6368650d 0a457870 69726573 |o-cache..Expires|

[Thr 2314] 700000001bdf430 000096 3a20300d 0a436f6e 74656e74 2d547970 |: 0..Content-Typ|

[Thr 2314] 700000001bdf440 000112 653a2074 6578742f 68746d6c 0d0a436f |e: text/html..Co|

[Thr 2314] 700000001bdf450 000128 6e74656e 742d4c65 6e677468 3a203137 |ntent-Length: 17|

[Thr 2314] 700000001bdf460 000144 38370d0a 53657276 65723a20 53415020 |87..Server: SAP |

[Thr 2314] 700000001bdf470 000160 4a324545 20456e67 696e652f 372e3030 |J2EE Engine/7.00|

[Thr 2314] 700000001bdf480 000176 0d0a4461 74653a20 4672692c 20323320 |..Date: Fri, 23 |

[Thr 2314] 700000001bdf490 000192 4a756c20 32303130 2031353a 33373a34 |Jul 2010 15:37:4|

[Thr 2314] 700000001bdf4a0 000208 3120474d 540d0a0d 0a |1 GMT.... |

[Thr 2314] -

---

[Thr 2314] <<- SapSSLRead(sssl_hdl=110c8cf30)==SAP_O_K

[Thr 2314] result = "max=65246, received=1787"

[Thr 2314] -

---

[Thr 2314] 700000001bdf3d0 000000 48545450 2f312e31 20343031 20556e61 |HTTP/1.1 401 Una|

[Thr 2314] 700000001bdf3e0 000016 7574686f 72697a65 640d0a63 6f6e6e65 |uthorized..conne|

[Thr 2314] 700000001bdf3f0 000032 6374696f 6e3a2063 6c6f7365 0d0a7072 |ction: close..pr|

[Thr 2314] 700000001bdf400 000048 61676d61 3a206e6f 2d636163 68650d0a |agma: no-cache..|

[Thr 2314] 700000001bdf410 000064 63616368 652d636f 6e74726f 6c3a206e |cache-control: n|

[Thr 2314] 700000001bdf420 000080 6f2d6361 6368650d 0a657870 69726573 |o-cache..expires|

[Thr 2314] 700000001bdf430 000096 3a20300d 0a636f6e 74656e74 2d747970 |: 0..content-typ|

[Thr 2314] 700000001bdf440 000112 653a2074 6578742f 68746d6c 0d0a636f |e: text/html..co|

[Thr 2314] 700000001bdf450 000128 6e74656e 742d6c65 6e677468 3a203137 |ntent-length: 17|

[Thr 2314] 700000001bdf460 000144 38370d0a 73657276 65723a20 53415020 |87..server: SAP |

[Thr 2314] 700000001bdf470 000160 4a324545 20456e67 696e652f 372e3030 |J2EE Engine/7.00|

[Thr 2314] 700000001bdf480 000176 0d0a6461 74653a20 4672692c 20323320 |..date: Fri, 23 |

[Thr 2314] 700000001bdf490 000192 4a756c20 32303130 2031353a 33373a34 |Jul 2010 15:37:4|

[Thr 2314] 700000001bdf4a0 000208 3120474d 540d0a0d 0a3c2144 4f435459 |1 GMT....<!DOCTY|

[Thr 2314] 700000001bdf4b0 000224 50452048 544d4c20 5055424c 49432022 |PE HTML PUBLIC "|

The last bit of the trace is as follows:

[Thr 2314] 700000001bdfa00 001584 703b4e6f 206c6f67 696e206d 6f64756c |p;No login modul|

[Thr 2314] 700000001bdfa10 001600 65207375 63636565 6465642e 3c2f623e |e succeeded.</b>|

[Thr 2314] 700000001bdfa20 001616 3c2f666f 6e743e3c 2f74643e 0d0a3c2f |</font></td>..</|

[Thr 2314] 700000001bdfa30 001632 74723e0d 0a3c7472 20626763 6f6c6f72 |tr>..<tr bgcolor|

[Thr 2314] 700000001bdfa40 001648 3d222346 46464646 46223e0d 0a202020 |="#FFFFFF">.. |

[Thr 2314] 700000001bdfb60 001936 73703b4e 6f206465 7461696c 73206176 |sp;No details av|

[Thr 2314] 700000001bdfb70 001952 61696c61 626c653c 2f707265 3e3c2f66 |ailable</pre></f|

[Thr 2314] 700000001bdfb80 001968 6f6e743e 3c2f7464 3e0d0a3c 2f74723e |ont></td>..</tr>|

[Thr 2314] 700000001bdfb90 001984 0d0a3c2f 626f6479 3e0d0a3c 2f68746d |..</body>..</htm|

[Thr 2314] 700000001bdfba0 002000 6c3e0d0a |l>.. |

[Thr 2314] -

---

I have replaced the company's name with company in the trace & the ABAP server's address with a.a.a.a and the java IP address with x.x.x.x

From the trace it seems to indicate an unauthorised connection and that no client modules succeeded.

Under security provider on the JAVA side, I have added the ClientCertLoginModule to the SAP-J2EE-Engine & I have also tried adding it to: com.adobe/AdobeDocumentServices*AdobeDocumentServicesSec_Config

I have been through all the ADS SSL guides I can find on the WEB as well as the configuration and troubleshooting guide.

Any suggestions?

Edited by: Jean Jacques Coning on Jul 23, 2010 6:49 PM

[former_member191062]

Hello,

please follow the weblog:

/people/dezso.pap/blog/2008/01/25/ads-ssl-configuration-journal-i-abap--java-640--70x

Best regards,

Dezso