|
| Re: BIRT WebViewer and Ports, dealing with HTTPS [message #902868 is a reply to message #902831] |
Mon, 20 August 2012 19:04   |
|
Changing the base href may work.
You could manually change the base href in the frameset fragment jsp or
put the base_url property in the viewer.property files
http://www.scribd.com/doc/44412235/Birt-Viewer-User-Guide#outer_page_9
Jason
On 8/20/2012 12:34 PM, Raishad Maharaj wrote:
> The short version of this is, is there a way to tell BIRT to use port
> 443 instead of 8280 (or whatever port the JBoss server is listening on)
> in the HTML BIRT generates?
>
> When I click on a report I get this window, it thinks about it for a
> while and then I get a browser prompt
>
> "Do you want to view only the webpage content that was delivered
> securely?"
>
>
>
> If I click ‘Yes’ the whole thing falls apart. If I click ‘No’ the report
> parameters dialog comes up OK, and then if I look at the HTML I find
> things like this:
>
> <TITLE>BIRT Report Viewer</TITLE><BASE
> href="http://server:8280/scereports/webcontent/birt"><!-- Mimics
> Internet Explorer 7, it just works on IE8. -->
> [snip…]
> <SCRIPT type=text/javascript>
>
> var soapURL =
> "http://server:8280/scereports/frameset?__report=report%2Fbilling%2FAccountSetup.rptdesign&__showtitle=false&__timezone=America%2FNew_York&__locale=en_US&__offsetMin=0";
>
>
> var rtl = false;
> </SCRIPT>
> Then when I click OK in the parameters dialog I get the browser dialog
>
> "This page is accessing information that is not under its control.
> This poses a security risk. Do you want to continue?"
>
>
> I assume that’s because clicking the OK button uses soapURL to redirect
> to another site/port than was used in the original request.
>
> The URL I am using to navigate to the report is https://server:443
>
> Httpd.conf is set up with a ProxyPass directive to redirect any request
> for /scereports on port 80 or 443 to the reports server on 8280. I
> assume BIRT figures out what port it’s running on from the servlet
> request and writes that URL into the HTML it generates. Is there a way
> to tell BIRT to use port 443 instead of 8280?
>
> I know that with the JBoss 5.1.0 SAML token environment we’re enabling
> SSL between Apache and JBoss and changing the ProxyPass directive to use
> the JBoss server’s SSL port. I’m working on that, but I’m not sure it’s
> going to get rid of the second message dialog, because it’s still going
> to be talking to a different port than the original request.
>
|
|
|
| Re: BIRT WebViewer and Ports, dealing with HTTPS [message #903222 is a reply to message #902868] |
Wed, 22 August 2012 14:31 |
 Raishad
Messages: 77
Registered: July 2009 |
Member |
|
|
Thanks, the viewer.properties change seems to be working
On 8/20/12 2:04 PM, Jason Weathersby wrote:
> Changing the base href may work.
>
> You could manually change the base href in the frameset fragment jsp or
> put the base_url property in the viewer.property files
> http://www.scribd.com/doc/44412235/Birt-Viewer-User-Guide#outer_page_9
>
> Jason
>
> On 8/20/2012 12:34 PM, Raishad Maharaj wrote:
>> The short version of this is, is there a way to tell BIRT to use port
>> 443 instead of 8280 (or whatever port the JBoss server is listening on)
>> in the HTML BIRT generates?
>>
>> When I click on a report I get this window, it thinks about it for a
>> while and then I get a browser prompt
>>
>> "Do you want to view only the webpage content that was delivered
>> securely?"
>>
>>
>>
>> If I click ‘Yes’ the whole thing falls apart. If I click ‘No’ the report
>> parameters dialog comes up OK, and then if I look at the HTML I find
>> things like this:
>>
>> <TITLE>BIRT Report Viewer</TITLE><BASE
>> href="http://server:8280/scereports/webcontent/birt"><!-- Mimics
>> Internet Explorer 7, it just works on IE8. -->
>> [snip…]
>> <SCRIPT type=text/javascript>
>>
>> var soapURL =
>> "http://server:8280/scereports/frameset?__report=report%2Fbilling%2FAccountSetup.rptdesign&__showtitle=false&__timezone=America%2FNew_York&__locale=en_US&__offsetMin=0";
>>
>>
>>
>> var rtl = false;
>> </SCRIPT>
>> Then when I click OK in the parameters dialog I get the browser dialog
>>
>> "This page is accessing information that is not under its control.
>> This poses a security risk. Do you want to continue?"
>>
>>
>> I assume that’s because clicking the OK button uses soapURL to redirect
>> to another site/port than was used in the original request.
>>
>> The URL I am using to navigate to the report is https://server:443
>>
>> Httpd.conf is set up with a ProxyPass directive to redirect any request
>> for /scereports on port 80 or 443 to the reports server on 8280. I
>> assume BIRT figures out what port it’s running on from the servlet
>> request and writes that URL into the HTML it generates. Is there a way
>> to tell BIRT to use port 443 instead of 8280?
>>
>> I know that with the JBoss 5.1.0 SAML token environment we’re enabling
>> SSL between Apache and JBoss and changing the ProxyPass directive to use
>> the JBoss server’s SSL port. I’m working on that, but I’m not sure it’s
>> going to get rid of the second message dialog, because it’s still going
>> to be talking to a different port than the original request.
>>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02915 seconds
] 
Search
Help
Register
Login
Home
