SSRS via Firepass

Posted By rdsohf5 on 10/10/2010 06:25 PM

 

Experts,

 

 

We have a .net reports page on our intranet site that uses the SSRS (SQL Reporting Services) web service to build a tree of reports and the Report Viewer control to display the selected report. To get this working internally I had to setup Kerberos authetication (otherwise you get the "double-hop" problem where the intranet site on one box tries to connect to SSRS on the other box as "anonymous").

 

 

However, when I login via Firepass and attempt to load the page I get this error...

 

 

Failed to list children: The request failed with HTTP status 401: Unauthorized. itemPath: Failed to set credentials: Object reference not set to an instance of an object.

 

 

I'm thinking it's because Firepass needs to be configured like my internal sites/boxes - i.e. the AD computer object should be set for Kerberos delegation, identity impersonate="true" added to the web.config and setspn applied to the HTTP path. But Firepass runs on linux and is an "appliance" with no entry in AD, so I don't know how to set it up for delegation

 

 

Has anybody else come across a similar problem? I'm a Database Administrator with little knowledge of the F5 and remote access. I've got network colleagues looking at the issue but thought I'd ask here is case anybody had some tips.

 

 

Also, I can go directly to the SSRS site from Firepass and view reports. However, when I run them in Internet Explorer the CPU shoots upt to 50% and the windows locks up. If I hide the SSRS toolbar they run OK. Strangely, I can run them

 

OK from Firefox with the toolbar showing. What could this problem be - some javascript thing?

 

 

Thanks,

 

RD

 

 

First off, how are you connecting?

 

 

Web Application Tunnel - Tunnel based

 

Portal Access - Basic Web stuff here

 

Network Access Tunnel - The device has an IP address on the network.

 

 

Second, how is the website coming up on Firepass?

 

 

Is it showing up Internet or Intranet?

 

 

Third, I have no idea about the double hop issue as all Intranet sites should always have automatic logon set. This is an option in IE.

 

 

If worse comes to worse we can always populate the username and password in the URL string if necessary.