You can use web director for a targeted SSL login in a mixed SSL/non-SSL web environment, so that every web-login request is redirected to and serviced by the SSL web engine(s) with all other requests being redirected to and serviced by the non-SSL web engine(s). This can be done in an environment with or without secondary servers. When this setup is in place, the HTTPS protocol must be used for all communications between the web client and the SSL web engines.
How to Implement an SSL Login Environment
To implement an SSL login environment, do the following:
**Note: In this example, CAisdsec is user-defined and can be renamed.
After you have run the pdm_perl pdm_edit utility to add the additional webengine and web-director, followed all the steps in the pdm_edit checklist, and have verified that it was given HTTPS and the appropriate port (normally 443 for IIS, or 8443 for tomcat), follow the next set of steps configure the webengines' configuration files appropriately to set the stage for the targeted SSL login.
Now that everything is configured correctly, please do a full recycle of Service Desk, and once it comes back up, test the login by attempting to access the non-ssl webengine using HTTP, and see if it automatically redirects you to the HTTPS secure webengine for login. Once you are logged in, it should automatically redirect you back to the non-ssl HTTP webengine for normal Service Desk activity.