.Net Webservice Authentication from Openedge Client

[Tony.Coventry]

Hi,
We are running OE10.1A on Windows XP/Server 2003 client, and recently started using MS Reporting Services 2005 with IIS 6


I have a generic GUI reporting screen which enables some fields for input depending on the report that has been chosen. To decide which fields to enable, I want to call a native Reporting Services webservice which tells me the parameters a particular report is expecting.


However, I have failed at the first hurdle. I hope this is something simple (security related), but allow me to describe what I've done so far.


I have the URL to the WSDL and can navigate to it in IE
I am using the WSDL analyser to generate the documentation an Progress code to call the webservice which works **when anonymous access is switched on in IIS** but when I turn on Integrated Window Authentication I get the following error:
proenv>bprowsdldoc "<URL>?wsdl" c:\temp\WSRepSer
Error loading WSDL document <URL>?wsdl : Cannot resolve URI: '<URL>?wsdl' status code: 401 (11748)


The above was probably not expected to work, but I have tried to use the -WSDLUserid/password options with a domain administrator account, but I still get the same problem:


proenv>bprowsdldoc "<URL>?wsdl" c:\temp\WSRepSer -WSDLUserid "****" -WSDLPassword "*****"
Error loading WSDL document <URL>?wsdl : Cannot resolve URI: '<URL>?wsdl' status code: 401 (11748)



As a workaround, we have created an 'in between' .Net webservice which has anonymous access enabled, and it creates a set of credentials (same as the aforementioned domain admin account), runs the Reporting Services webservice and returns the output to Progress
I can use the WSDL analyser on this webservice since it does not require authentication.

proenv>bprowsdldoc "<URLPassThruWS>?WSDL" c:\temp\WSPassThruTest
Documentation written to file:///c:\temp\WSPassThruTest/index.html
<FONT size=2>This works, but ideally we would like to expose the other Reporting Services webservices to the Progress client (without compromising security by enabling anonymous access)

Sorry for the long-winded post. I hope I have provided enough detail.
Any help would be greatly appreciated.


Regards
Tony Coventry
--------------------------
Systems Development & Application Support
Doosan Babcock Energy Limited
Porterfield Road, Renfrew PA4 8DJ

Tel:

 

[grendal]

We're looking to do something similar here.

Is there any chance of viewing the code for the 'in between'?

Regards,

 

[Tony.Coventry]

Here is the snippet that forces the credentials. HTH


using ReportingServiceTWS;
.
.

// Create reporting services object
ReportingService2005 RSWS = new ReportingService2005();
// Default method
// RServices.Credentials = System.Net.CredentialCache.DefaultCredentials

// Forced credentials
ICredentials creds = new NetworkCredential("loginID", "password", "domain");
RSWS.Credentials = creds;