InfoPath Dev

Hi all;

I'm new to InfoPath development and have the following outstanding issues/unknowns:

I'm developing a Form that submits to a WebService and also runs queries from the WebService.

All works fine at this point I can Submit (via the regular Submit button in the menubar) and I can query via a "Run Query" button that was added

from my Receive data connection.

The thing is that I need to get some values back when I Submit to the WebService; I did some research here at InfoPathDev and ended up adding a (secondary) Receive connection that I connected to the Submit method on my WebService, by doing this I can receive data when calling the WebService.

I also added a button to the form, when clicked a VB script fn gets called.

From within the On_Click fn I would like to do the following:

      1- Navigate and retrieve the "selected" item on my form (I have a Master/Detail Interace, the master contains line descriptions of my main bussines entity and the detail contains all the data) In fact I want to submit the object that is currently selected

      2-Call my secondary Receive connection method passing the data retrieved (from the Form, in -1 above)

      3- Take the returned data and modify some elements (ID and RowVersion) on the selected item (from the Form, in -1 above)

      4- Please sombody give me a hint or directions (links) on how to deal with users, I want to know and track who is submiting forms to the WebService

          I'm using ASP.NET to implement the WebService and IIS6 (and II7) to run-it/publish it, what are my best options here ? Windows Authentication ?

          other ?

Guidance, and samples would be higly appreciated 

Thanks

Guillermo

Hello,

For local intranet, you would use an ASPX page to authenticate the user and serve up the XML, but you can't rely on Windows Authentication via your domain since people are coming from outside of your domain.

Someone can create an InfoPath solution and stick it in their cache and then save the XML form to desktop and open it up offline. The solution could be reverse engineered to ignore the user/password, so this is not good. Of course, people can also just save the xml and open in Notepad... :) If you are hiding sensitive information in the xml file, you'll want to at least encrypt it.... better yet, don't put any sensitive data in there!

You need some kind of authentication in your middle-tier. You could create a web page that forces users to login against a server-side database before sending the XML file down, but people can still save the XML and send it to someone, so you lose Information Privacy for the sample form.

Why not just remove the sensitive information in the SampleForm and try to load it from a secure site onload? Then, you can have the user authenticate against the secure site using the built-in dialogs.

In general, you'll have to restrict access, and reduce sensitive data