Re: Steps to setup app allowing offsite network access using IIS Authe
- From: Gerry Hickman <gerry666uk@xxxxxxxxxxxxxxxx>
- Date: Sun, 08 Jul 2007 00:48:17 +0100
Hi,
I'm not sure what you're asking?? The first paras imply you want them to be able to _run_ a web app on an IIS server? You keep using the word "run". Obviously anyone can "run" a web app just be browsing to it.
Do you mean you want them to be able to collaboratively develop a web app. If so, you may want to look at source control over HTTP and a means of publishing over HTTP such as FrontPage or WebDav.
Do you mean you want them to be able to compile and debug on the live server? If so, that's another (long) story.
Regardless of all that, one problem to look out for is that they won't have Active Directory if it's in a DMZ, so Integrated Authentication won't work, nor will Impersonation, You'd need to use plain text with SSL, nasty, and you'd need to pass the passwords as plain text if you want them to be able to start a process, unless you can get Kerberos working in the DMZ and able to pass the tickets over two hops. If they really are "partners", you might be better off with a VPN.
Ever thought of using Linux instead?
thejamie wrote:
In order to create an application our partner's can run from a website in our DMZ, there will be several steps involved - from compiling the application with a strong name, to setting up IIS (framework 2.0 and vs 2005) and finally access to the application which will need to run on a server from the DMZ for our partners. Question:
Can anyone outline each step required to set this up on an IIS server in the network or DMZ along with the assembly requirements of the application to run on this network?
Or is there a link to a web page that shows, step by step, (or outline) of the process that creates an application, creates the IIS that exposes the application in the DMZ (or even in the network) securely, and allows the application to run from this location?
Even just a list of all the steps required that allow the application to run on the network would be appreciated (ie inside the network rather than from the DMZ).
Network is already established and secure and DMZ has been available via FTP for several years (we want to retire our use of STX). The problem is primarily permission setup in NET Framework 2.0 (CAS) permission end. Click once works fine but it is not what we are looking for. Instead we need a method that specifically assigns an "application" to be run only from the network [not as a service on the server and not as an application that installs on someone's local machine from a network location]. Our partners will only be able to come in through IIS authentication. Our partners need the ability to kick off specific processes on our server when they deem it necessary.
--
Gerry Hickman (London UK)
.
- Follow-Ups:
- Prev by Date: Re: VS Source Control removing binding??
- Next by Date: Re: Repost of an old question. Can not use Access in VS2005
- Previous by thread: Re: Exclude Folders VS 2005
- Next by thread: Re: Steps to setup app allowing offsite network access using IIS A
- Index(es):
Relevant Pages
|