Built a fairly complex web database application in PHP & MySQL. It works great on my UNIX server.
Turns out I've decided I should serve the application on the corporate intrAnet server, so it can be internal-only without the inconvenience of users having to log in to the private web pages.
But the intranet server is IIS with ASP (and they don't plan to install PHP). So I'm looking for a way to avoid re-writing the whole application in ASP, with which I'm not familiar.
I'm looking for a way to keep the data-intensive pages on the UNIX server with PHP/MySQL, and just make a couple of "doorway" pages in ASP, which would get users into the UNIX-served pages.
Easy enough, but this needs to be transparent. Instead of getted prompted for a UNIX Basic Athentication login when moving from an IIS/ASP page to a UNIX/PHP page, I want to make the few ASP scripts send the Basic Authentication info to the UNIX server. That way, users behind the corporate intrAnet would not have the inconvenience of logging in to the basic authentication popup whenever they open one of the UNIX-hosted pages.
Sending basic authentication is possible with some PHP functions, but I need to do this with ASP.
What function or commands can I embed into the ASP form or script so that they will send basic authentication user/password info to the protected pages on the UNIX site? So the ASP users will not have to know or input a user/password when accessing one of the unix pages?