ESS broke after SSL turned on in portal (https)

[Former Member]

Hi SDN

We turned on the SSL (HTTPS) on port 50001. Portal seem to work fine but the ESS services does not even open up. The ECC system is http. Is this the issue? or Am I missing any additional configuration?

Thanks, Raj

[rainer_fux2]

Hello,

I have a similary problem. The portal server is running on HTTPS. I also changed to HTTPS for all ABAP Webdynpros on the backend. I can access them successfully via SICF. But when they are accessed on the portal, the message "This website cannot be shown" appears.

I deactivated the HTTP service in SMICM.

We are using ESS WDA on the portal.

Did you get a solution for this?

Regards,

Rainer

[Former Member]

Are you using Web Dispatcher? For portal, backend or both? If you have deactivated HTTP in the backend system, you have to configure Web Dispatcher to query the message server using HTTPS. Use Fiddler, HttpFox, HTTPwatch, etc. to find out what URL is being accessed when you get the error.

[rainer_fux2]

Thanks.

Yep, the Web Dispatcher is configured. In fact, I found a solution for my problem. On the portal side (in System Landscape) the HTTPS-Port was wrong. There was little confusion between 8443 and 8433. 😉

Best Regards,

Rainer

[Former Member]

Could be, at least you should get a browser warning popup saying that the page has both secure and non-secure content. Verify with Fiddler, HttpFox, Httpwatch, ...

What EP version? What ECC version? Are you using a reverse proxy / load balancer? What browser are you using? Try to enable mixed content in the browser settings to see if it helps.

[Former Member]

Thanks Samuli.

We are in EP 7.31 and ECC EhP6. So all ESS/MSS content are in WDA and the browser I use is IE8. MSS iViews seem to work, but still have to extensively test it. But ESS when I click personal profile, it just shows a Javascript void(0) eror at the bottom of the page and does not do anything. When I login with http then everything seem to work fine.

I am not using reverse proxy/load balancer etc, it is a direct access. I am using ctrix and they dont have the http watch included to the browser. I can check with someone onsite in the morning. Since citrix, I dont have many options to change in the browser.

Thanks, Raj

[Former Member]

I can confirm your observations. The ESS WDA applications use Launchpad for navigation, which in turn uses the transaction launchers inside the ERP common role. Looks like the Launchpad is triggering the portal event but the portal integration API is not processing it meaning the ERP common role is never invoked.

[Former Member]

Thanks again Samuli. Is it a known issue when https is turned on? I could not find anything in SCN. It would be great if could suggest a fix.

Thanks, Raj

[Former Member]

Actually I think that it is a generic restriction when using WDA in a portal environment. See SAP note 945516 for details, paragraph "Internet protocol: http or https".

http://service.sap.com/sap/support/notes/945516

[Former Member]

You can use SAP Web Dispatcher to terminate SSL, then use HTTP between WD and portal as well as WD and ECC.

[Former Member]

After doing https, then you have to update the System config, it should point to https and respective https ports.

[Former Member]

Thanks Samuli for your prompt reply. The note clearly says ECC and portal should use same protocol. The main reason client wanted to turn on SSL because of personal sensitive information like paystubs etc. So using webdispatcher route would give up the whole reason behind SSL. I guess we have either use http or change the ECC services to https.

Thanks Yugandhra. Yeah we have to first convert ECC services to https and then change the system settings.

[Former Member]

I take it that you are aware that enabling HTTPS on portal doesn't enable HTTPS for any Web Dynpro ABAP applications you might run inside the portal? Even if the applications are accessed from the portal the connection is between the client and the backend system. So if any WDAs are in scope and the customer has asked for secure network communication, HTTPS has to be enabled in the backend regardless of the restriction described in SAP note 945516.

[Former Member]

Agreed Samuli. In the process of enabling https in the back end. Will keep you guys posted. Thanks much.

Thanks,