URL Reporting in Crystal Enterprise(CE) 10

[donly1k]

We have been using Crystal Report RAS 9 for some time now and we are planning to migrate all reports to CE10 Crystal Enterprise (CE).


Currently, to provide users access to the reports in CR RAS 9, we just place a URL within their application that links directly to the reports. For example, within Cold Fusion web applications we include a URL to call a report (*.RPT) on the web server Crystal Report 9 RAS, then the report is launched in the crystal report viewer and customers can see it or print. See example:

http://MySERVER/crystal/En/ASP/rPor...:\Crystal\MYDEMO\MYFOLDER\MYREPORT+%SHEET.rpt

We are having difficulty determining how to do construct a URL to access the reports published in Crystal Report 10 CE.


We have published the reports via Crystal Wizard version 10. The published reports are assigned a unique ID within Crystal E-portfolio. We are also using single sign on (SSO), so our authentication type is Windows AD.


With the new version of Crystal I am unable to capture the URL and submit it from a Cold Fusion application, because it appears to require a logon to the E-portfolio environment. Then the user has to click on Windows AD as the authentication type, and click login before the report parameter screen will be displayed. Even if I add the parameter to the URL string for the authentication type of WindowsAD, the user is still presented with the Crystal login screen.


Any advice you can give will be greatly appreciated.

Thanks

 

[Turkbear]

Hi,
Review the CE8 Command line options doc at BObj's Support site..
Here is one way ( includes passing a parameter):

http://yourceserver/viewrpt.cwr?id=...erprise&init=actx&promptex-WORK_REQUEST_NO=12

For other authentications, etc. you may need to add a apspassword parameter..

 

[hahu2000]

Hi,

I am using secEnterprise authentication just as given above, but is there any way not to pass passwords in clear text... how can i make the url reporting more secure ?

 

[KingfisherINC]

You can't make URL reporting more secure - That's just one of the problems with it, as it uses HTTP GET.

However you can use HTTP POST and hide all the parameters, ids, passwords, etc.

There are examples in the CE SDK help files on your CD.

Kingfisher [CECP]