Hi,

I have the following scenrio and was wondering best way to go about it in ensure future compatibility with DNN updates.

I have a main portal with sub portals hung off it. In each sub portal it collects data for producing address labels.  In the windows forms application I query the portalid and return the labels.  However, I now want to secure it up.

Rather that right my own login system i'd rather call the DNN tables directly, as its attached to our VPN to our DNN server on the internet.

What's the best way to validate the Username and Password is validate in order to log them into the local windows forms application?

Look at the iWeb thinger from Michael Washington.  It is a webservice that supports authentication and the like, would be a lot easier (and cleaner) than direct table access.  His link is: http://iweb.adefwebserver.com/

---

-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com

Yes the problem with direct table access is that when you upgrade the DotNetNuke site and the Core changes something your code will break  (this happens a lot as things are constantly improved).

IWeb uses the DotNetNuke API and does not directly access the Core tables. You can either use IWeb or simply copy the code you need from IWeb. IWeb also has an example Windows Forms client that authenticates with your DNN site. Source code is included.

---

Michael Washington
http://ADefWebserver.com

A Free Open Source DotNetNuke Help Desk Module