Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
URL for BIRT reports
suma
hi all,<br />
I have created some reports in BIRT and deployed it in Actuate iserver. The url for the reports is in this format<br />
"<br />
<a class='bbc_url' href='
http://localhost:8900/iportal/executereport.do?__executablename=/PathToReport/ReportName.rptdesign&MyParam=ParamValue&invokesubmit=true'>http://localhost:8900/iportal/executereport.do?__executablename=/PathToReport/ReportName.rptdesign&MyParam=ParamValue&invokesubmit=true</a><br
/>
"<br />
but whenever i tried to open the report using this url it asking for the login username and password for actuate server..how could i avoid this ???<br />
<br />
<br />
Thanks ,<br />
Suma
Find more posts tagged with
Comments
averma
Hi Suma:<br />
<br />
One way to bypass the login screen would be to embed the username and password information within the URL. e.g.<br />
<pre class='_prettyXprint _lang-auto _linenums:0'>http://localhost:8900/iportal...........&userID=username&password=xyz</pre>
<br />
iServer offers a security model that could be customized to implement your own authentication and authorization as well. <br />
<br />
Ashwini
rmurphy
Suma,<br />
You have a few choices. <br />
1. You can pass a valid username/[password] over the URL.<br />
2. You can implement a security adapter to tell the iServer Express who is accessing the environment.<br />
<br />
For option one, you would simply append &userID=yourUserID and if the user has a password you would also append &password=yourPassword. Obviously this approach is not ideal for environments where security is of any substantial concern. To make this a bit more secure, your application could submit a POST rather than a GET to prevent the URL from being visible in the URL.<br />
<br />
For Option two, you would implement a Java class that would plug into the iServer Express interface (iPortal). This class is responsible for telling the iPortal who is attempting to access the environment. This extension point is what is used to integrate with existing security infrastructure or single sign-on solutions. You can read more about the in the following manual in the "Creating a custom security adapter" section. <br />
<br />
<a class='bbc_url' href='
http://www.birt-exchange.com/documentation/Manuals/creating-custom-iportal-apps.pdf'>http://www.birt-exchange.com/documentation/Manuals/creating-custom-iportal-apps.pdf</a><br
/>
<br />
<br />
Rob