Hello:

I wondering what is the best way to run and force authentication (login) in MWS with https, and, after successful login go back to http.

Any help or recommendation will be appreciated.

Regards.

Norberto.

There is a solution for this provided in these official fixes:

• MWS_8.2_SP1_Fix13

• MWS_8.0_SP2_Fix18

This is how it to use the new component:

1. Deploy the components/extras/wm_httpsredirect.war to MWS
2. Open the ‘Cluster Administration’ portlet and do this:
   a) Make sure there is a non-zero https port defined
   b) Make a note of what the front end url is configured as
   c) If any changes were made, restart MWS
3. In a new browser window, open the front end url (i.e. http://localhost:8585)
4. In the address bar of the browser verify that the login page has switched to a secure address (i.e. http://tech.forums.softwareag.com:8587)
5. Login
6. In the address bar of the browser, verify that the address has switched back to the non-secure address (i.e. http://localhost:8585/current.user.start.page)

Eric:

Ok, I’ll try.

thanks a lot.

Regards.

Norberto.

Hello Eric:

One more question: how can I undo the changes? deleting the wm_httpsredirect.war and components?

Best regards.

Yes, to undo the changes, you would just uninstall the wm_https_redirect.war file.

If that doesn’t work, you may also need to restart the MWS server to clear out anything caching the old configuration.

Hello Eric:

I need to do the same thing in V9.7. Do this .war work in v9.7? Or Do you have a .war for v9.7?

Thanks in advance.

Regards.

Norberto.

Sure, there should be a components/extras/wm_httpsredirect.war in the 9.7 distribution.

Hi Eric,

I also tried using wm_https_redirect.war, i can see there is auto redirect from http => https during login, but after login it is failed to switch back to http, apart from the war file deployment are there any other things that we need to change.

Regards
Sreeni

This is what it should be doing:

1. Check if a non-zero https port is configured in the cluster config (as configured in the Cluster Administration page). If not, ignore the request since https is not available.
2. Get the frontEnd url from the cluster config and compare the incoming request to check if it starts with the configured frontEnd url. If not, it might be direct connection to the node, so ignore the request. This is for devs and admins to connect directly to a cluster node (for example, to bypass the loadbalancer) to correct problems if something goes wrong.
3. Calculate if the request requires switching the request scheme (http to https, or https to http). If yes, send an http redirect and a copy of the cookies to do the switch.

So when rendering the login page it should switch to https://[frontEndUrl]/… and then after login it should switch back to http://[frontEndUrl]/…