v9 - Login to Metastorm via ECL fails in windows client but working in Web application

I am using the ECL to login to metastorm in order to raise a flag from a windows service running on the same machine as the engine. When I attempt to create a new metastorm session I get the following error:

*************************************************

Failed due to: System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate,NTLM'. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   --- End of inner exception stack trace ---

*************************************************

In IIS I've set the ECL.WS application to Anonymous Authentication and Identity = Application Pool and assigned it to the MetastormECLWSAppPool . I set the MetastormECLWSAppPool to LocalSystem as the Identity. Also WIndows Auth is set to NTLM and Negotiate.

*************************************************

In the App.Config I've set the following as the service model

<system.serviceModel>











   http://localhost/ECL.WS/Service.svc" binding="basicHttpBinding" bindingConfiguration="MetastormECL" contract="Service" name="MetastormECL"/>

</system.serviceModel>

*************************************************

The application is using Metastorm.ECML.Client.Net;

and the call to Metastorm fails the minute I attempt to create and instance of IMEtastormOperation

public

staticIMetastormOperation metastormSession = newMetastormOperation();

- This times out each time

*************************************************

Anyone know how this is supposed to be configured? Please note SSO has been setup and modified to work within this organizations unique sso structure and using a similar style of code in a web application to create a new session works without a hitch

Find more posts tagged with

BPM

Comments

DSmith

Update: I changed the Wep App Pool to .NET 4.0 to match the applications target and now I get the following:

The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8)

DSmith

I resolved this by making some configuration changes. Please note that I made a seperate copy of the metastorm ECL.NET web service so that I could get this to work with a windows client without effecting the web client that I already have using it. as indicated in the 1st step.

I hope someone else finds this useful because this was a chore to configure properly.

Created a Second copy of the ECL.NET Web service
Configured this new Service as a separate web Application
Set the Identity of this site to the Metastorm Service Account
Set the Application Pool to an app pool running under the Metastorm engine user
Set Authentication on the Web Site and application Pool to Anonymous
Changed the Web.config for this site to None for Security
Set the Same for this applcations App.config File
Binded the site name to match the url in IIS as opposed to localhost/etc/Service..
Added that Binding to both the App.Config and the Web.Config
Added Impersonation to the App.Config so that the Application will run as the Metastorm Service Account.

Another useful thing I did was to add the following debugging code to the webservice between the system.servicemodel and application Settings

Which assisted me in seeing if I was hitting the service or not.

In my application I also noticed that the service was still taking the localhost as its url so I modified the call: In the the MetastormOperation can be called with an overload in which you include the location of the service

as such

metastormSession = new MetastormOperation(ServiceURL);

Which you will need if you have 2 versions of this service on your server, changing the endpoint address in the app.config of my applcation did not properly point it to where I needed it to go.