on 09-07-2010 11:26 AM
Dear Experts,
I have an odd issue with SSL certificate on my backend ABAP prod system. When calling a webdynpro page via https i get a "untrusted certificate" message, and my portal is unable to display the content unless accepting the page is not trusted. When i export the "SSL Server Standard" certificate it is complete with CA root and everything, "certificate is ok". but nevertheless i cant get the certificate to show in the browserbar, the certificate is a "selfsigned" certificate showing issued by *.companyname.com. I tried to export the PSE certificate and server ssl certificate, and none of them is *.companyname.com certs.
I restarted SMICM and all that stuff, I even implemented the solution on our QA environment and there it works. But i cant get the cert active on prod environment.
Anyone has a suggestion where it gets the *.companyname.com cert from if its not strustsso2?
thanks in advance!
Kind Regards,
Soren
Hi,
>Anyone has a suggestion where it gets the *.companyname.com cert from if its not strustsso2?
Do you have a SAP Web Dispatcher in front of your ECC system ?
On my ECC system, the SAP WEb Dispatcher is the one in charge of the SSL business and is the only one to get a signed certificate. On ECC6, the certificate is self signed.
Regards,
Olivier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Olivier,
I actually have an SAP Web Dispatcher in front of the system - I know the certificates between them are self signed because its enough that theyre known between them (added to pklist). Your answer very much makes sence, and i will try to run a http watch to see if i can find the sender of the certificate.
I havent thought of it this way before. That really gave me something to work with, thanks a lot!
Kind Regards,
Soren
Hi everyone,
Meanwhile i figured it out. It was infact the webdispatcher which was making problems, but as I found out it was due to the current kernel version. When i updated the kernel communication was established right away. So the setup was ok, but Kernel version made it impossible to make it work.
Thanks everyone for helping me towards this solution.
Kind Regards,
Soren
Hi,
The issue seems to be because of an expired certificate. Check the validity and if needed recreate the certificate and import it again into ur portal system.
Regards,
Varadharajan M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.