ComputerSystemsNetwork 7/23/2009 9:55:37 AM

eConnect - security risks?

I am running into a dilemma.  I am using eConnect with integrated security and have the UI and eConnect Call method all in the same code.  This requires the user running the eConnect UI Interface to have integrated security on the domain as well as be part of the GP SQL Server.  I know there is also an option to create a Windows or Web Service.  This way you use a single domain account to call the eConnect method based on a specific folder on the server.  This way your eConnect UI is separate then the importing of XML file into GP.My IT department thinks there are risks associated with option #1 b/c users become part of the GP SQL Server.  If I use option #2  (using Windows or Web Service), how do I capture eConnect exceptions?  With a number of calls being made to eConnect using the service, how does one isolate errors and send them back to the eConnect UI (end user).Any thoughts?




Version: Unknown or N/A
Section: eConnect

Table Definition Quick Links
All Tables
SOP Tables
RM Tables
GL Tables
POP Tables
HR Tables
PM Tables
UPR Tables
IV Tables
Olympic Tables