CNC Traveler
Member
Here is our basic issue. When we went to 8.12 it was decided to deliver the web E1 application via a published application using Citrix. We also are delivering via the web for some users via IIS servers in the DMZ. We then use an OC4J connecter to our backend OAS application servers. With going to the 9.1 tools release we need to re-evaluate the method we provide access to the JD Edwards systems since we need to use WebLogic now.
My IT infrastructure group wants us to move all users to the Citrix solution because it provides one place they need to provide security along with the inherent issues we would face with users running different browsers along with the plugin issues (Not to mention the different flavors of web applications we have). This makes a bunch of sense if we look at this from only a support/security issue. I know the users do not like using Citrix when they do imports/exports just because of the extra steps to get the files to and from the Citrix server. Then you throw into the mix the direction of Oracle with web functionality and mobile devices and Citrix becomes a limiting factor or at least an unknown. Using gestures becomes a concern and the need for the application to interact with the browser, expecting it to be local to the machine they are running.
My infrastructure guys are discussing options of delivering JD Edwards via web architecture but we need some guidance on best approaches. Some of the options they are playing with right now are; authenticated SSL Proxy, SSL Proxy and the least desirable being straight HTML pass thru which they will not agree to put in place.
I'm looking for some best practice suggestions for secure/reliable web delivery. We want to keep the hackers out! As we know, vulnerabilities are identified every day.!
My IT infrastructure group wants us to move all users to the Citrix solution because it provides one place they need to provide security along with the inherent issues we would face with users running different browsers along with the plugin issues (Not to mention the different flavors of web applications we have). This makes a bunch of sense if we look at this from only a support/security issue. I know the users do not like using Citrix when they do imports/exports just because of the extra steps to get the files to and from the Citrix server. Then you throw into the mix the direction of Oracle with web functionality and mobile devices and Citrix becomes a limiting factor or at least an unknown. Using gestures becomes a concern and the need for the application to interact with the browser, expecting it to be local to the machine they are running.
My infrastructure guys are discussing options of delivering JD Edwards via web architecture but we need some guidance on best approaches. Some of the options they are playing with right now are; authenticated SSL Proxy, SSL Proxy and the least desirable being straight HTML pass thru which they will not agree to put in place.
I'm looking for some best practice suggestions for secure/reliable web delivery. We want to keep the hackers out! As we know, vulnerabilities are identified every day.!