Hi,
We have set up a server in our DMZ to handle Web reporting using our BOEXI R2 system ( Windows Server 2003, IIS6 based) .
We use a Reverse Proxy ( on an Apache server running RedHat) to minimize the # of ports needed to be opened in the firewall and all works fine..
With this URL, for instance:
The report runs fine ( if needed, if prompts the user to install the JRE )...
The same URL, but with the viewer specified as actx, still runs the report but it prompts the user to re-enter the username/password before the viewer displays the report..
After the first time in a session it does this, any other report requested ( by changing the ID number, for instance) runs without prompting for that info..
Does anyone know why that viewer, and only that viewer, needs this extra login?
To Paraphrase:"The Help you get is proportional to the Help you give.."
We have set up a server in our DMZ to handle Web reporting using our BOEXI R2 system ( Windows Server 2003, IIS6 based) .
We use a Reverse Proxy ( on an Apache server running RedHat) to minimize the # of ports needed to be opened in the firewall and all works fine..
With this URL, for instance:
The report runs fine ( if needed, if prompts the user to install the JRE )...
The same URL, but with the viewer specified as actx, still runs the report but it prompts the user to re-enter the username/password before the viewer displays the report..
After the first time in a session it does this, any other report requested ( by changing the ID number, for instance) runs without prompting for that info..
Does anyone know why that viewer, and only that viewer, needs this extra login?
To Paraphrase:"The Help you get is proportional to the Help you give.."