A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.
We have a desktop s/w (.NET/C#) that needs to talk to a web server and do some stuff.(Pull some data, send some data). The channel would be https, and before it does anything, it needs to authenticate (send login/pwd).
I'm familiar with some of the issues, but looking for some good links/resources/tips.
Tuesday, September 20, 2005
To make a page use HTTPS, just make the ASP.NET script check whether the URL used to get to it starts with https.
For scripts expected to be used in intranets or extranets where the corporate entities share workgroups and or active directories, your best bet is Windows Authentication. For websites that may handle god-knows how many users and the user/pass backs to the DB--custom authentication is your game. To get a sense of how things work in ASP.NET 1.1 took me a little while, but I am bit slow--and I wanted to write a kick ass ACL library to go along with the authentication module. But if you keep it simple, most basic books on ASP.NET 1.1 should take you most of the way. Essential ASP.NET from Addison-Wesley will do, MSDN will take care of the rest if you are still confused.
Authentication and Authorization happens to be one of the module implemented by the Patterns and Practices Group at Microsoft. The producer of Enterprise Library. It's a time-saver, and your time invested in learning it could save you a ton of trouble--especially if you didn't get into the ASP.NET business to get your fix of Architectual Astronaut angst (like I am).
This topic is archived. No further replies will be accepted.Other recent topics
Powered by FogBugz