Forum Discussion
Ski_Kacoroski_2
Apr 05, 2017Nimbostratus
Yes, the kronos URL is insecure and they have no plans to fix it for at least a year. So the URL is http://kronosf5.nsd.org/wfc/applications/wtk/html/ess/logon.jsp. What I would like is for the F5 to sit in front of the Kronos system and offload the SSL stuff so instead of a redirect which I am doing now, I want a forward (or something). The problem with a forward is I cannot figure out how in a policy to do a forward and rewrite '/' to '/wfc/applications/wtk/html/ess/logon.jsp' for the initial logon and then have all other URLs just get passed through the F5 with the F5 dealing with the SSL part between the client machine and itself. Hope this helps to clarify the problem. Thanks for responding.