cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SSL setup with a load balancer

Former Member
0 Likes
566

We are running EP 7.0 SP14 and have set it up to run through a Cisco ACE loadbalancer. We have also setup SSL with the certificate on the ACE load balancer. Everythign work fine, except we keep getting a Security Alert popup message in IE that states "You are about to be redirected to a connection that is not secure."

Are there some additional configurations that I need to do in EP to make this go away?

Maximum points to the first correct answer.

View Entire Topic
ravi_joseph
Active Contributor
0 Likes

maintain the portal HTTPS URL (https://fqdn:50x01/irj) in your loadblancer url settings,

to avoid this alert you need to maintain https access to all your backend system connections, as slava suggested do a trace with the http watch and identify the where the switch happens from https to http .

jo

Former Member
0 Likes

There are 2 areas that we consistantly see this message, one logout and when running a VC application. Using IEWatch, the URL of the logout does change to http. However, I can not see the URL change to http for the VC app. My guess is that the non-SSL call is occurring within the VC application, and therefore not recorded by IEWatch.

How do I change the URL call of the logout to https?

Does anyone know what to check for within the VC code?

Former Member
0 Likes

You can change logoff URL to any value:

http://help.sap.com/saphelp_nw04s/helpdata/en/44/aada5230be5e77e10000000a155369/frameset.htm

Regarding VC apps.

It is strange you cannot see HTTP in the IEWatch. IE should not be able to alert about something it does not see. I suggest you to use something more substantial to trace network calls: http://www.wireshark.org

This is the best tool I know for network tracing.

Regards,

Slava

Former Member
0 Likes

We switched the logoff URL to [https://<portal>/] and when the user logs off, it does forward them to this URL, but then the server redirects the browser to [http://<portal>/irj/portal]. The server does not know that it is secured. Plus, the logon screen is still posting to the unsecured URL.

Is there a setting in Portal or in WAS that we need to set specifying that the application is secured?

Former Member
0 Likes

Try to use logoff URL https://<portal>/irj/portal instead of https://<portal>/

Former Member
0 Likes

We needed to configure the Proxy Mapping setting in VA.

[http://help.sap.com/saphelp_nw70/helpdata/EN/b8/437d46d4451e4c9ab756e272a1581d/frameset.htm]