Hello All... We're developing a webpart-enabled application. We quickly see that some sort of authorization mode is required - for storing personalization information. To get ourselves off the ground, we just turned on windows authorization inside the web.config.
But part of our application includes authorizing users against a third party customized computer - the communications with this computer is via a proprietary tcp/ip socket connection. The communications with this computer is straight forward for us...
Is there any way we can use the authorization from that computer to support asp.net's authorization requirements? We'd rather not have to have the user log onto windows then log onto our 3rd party computer. Note, we're not trying to just store the data in some other database, but we'd like to send a username/password to this other computer then populate whatever data asp.net needs in order to identify the user. As far as we're concerned asp.net can still maintain all the personalization data in the sql 2005 express database.
Thanks!
Curt