2 Replies Latest reply on Jan 3, 2008 11:40 AM by pchris1977

    Problem with https web service

    pchris1977
      I setup an sql server 2005 endpoint over SSL channel (needed for basic or digest authentication).
      I try to connect to this webservice from a flex application:
      <mx:WebService id="wWs" wsdl="https://mycomp/sql/myap?wsdlsimple"
      fault="handleFault(event)">
      <mx:operation name="myop" resultFormat="e4x" result="handleLogin(event)">
      <mx:request>
      <cUser>{user.text}</cUser>
      <cPass>{parola.text}</cPass>
      </mx:request>
      </mx:operation>
      </mx:WebService>

      On local computer it works fine. But when I try to work from another domain I get "Seccurity error accesing url". Both of application and webservices is on the same computer and work on ssl port. I try to use SOAPHeader for DIGEST authentication but it does not work (maybe I don't know how to work with that).
      When I try to use wWs.setCredentials("user","password") the error: "Authentication not supported on DirectHTTPChannel (no proxy)." appears.
      I added useProxy="true" but the error: "MessagingError" message='Destination DefaultHTTPS' either does not ..." I don't know hot to configure flex working with destinations.

      So if you can, please help me.
      Cristy
        • 1. Re: Problem with https web service
          Level 7
          The setCredentials() API is only for communicating with the LCDS Proxy Service.

          Your first thought of using SOAP headers is the correct way to do this, so
          what version of Flex 2 are you using?

          Pete


          Hello pchris1977,

          > I setup an sql server 2005 endpoint over SSL channel (needed for basic
          > or
          > digest authentication).
          > I try to connect to this webservice from a flex application:
          > <mx:WebService id="wWs" wsdl="https://mycomp/sql/myap?wsdlsimple"
          > fault="handleFault(event)">
          > <mx:operation name="myop" resultFormat="e4x"
          > result="handleLogin(event)">
          > <mx:request>
          > <cUser>{user.text}</cUser>
          > <cPass>{parola.text}</cPass>
          > </mx:request>
          > </mx:operation>
          > </mx:WebService>
          > On local computer it works fine. But when I try to work from another
          > domain I
          > get "Seccurity error accesing url". Both of application and
          > webservices is on
          > the same computer and work on ssl port. I try to use SOAPHeader for
          > DIGEST
          > authentication but it does not work (maybe I don't know how to work
          > with that).
          > When I try to use wWs.setCredentials("user","password") the error:
          > "Authentication not supported on DirectHTTPChannel (no proxy)."
          > appears.
          > I added useProxy="true" but the error: "MessagingError"
          > message='Destination
          > DefaultHTTPS' either does not ..." I don't know hot to configure flex
          > working
          > with destinations.
          >
          > So if you can, please help me.
          > Cristy


          • 2. Re: Problem with https web service
            pchris1977 Level 1
            I am using Flex Builder 3 Version: 3.0.190133 and I try to connect directly (without .NET or other middleware) to an SQL Server 2005 (or 2008) HTTP Endpoint (for SOAP).
            I want to try BlazeDS DataService, but when I found that I need to install TomCat or Appache or any other J2EE environment I was discouraged to do this.
            SQLServer 2005 HTTP Endpoint (for SOAP) is supporting over SSL (basic, digest , kerberos, ntlm and integrated) security.
            Internet Explorer ask for user and password (if Basic Security), and the connection is working fine. But, if I want to connect directly from Flex (without authentication from Windows appears) I don't know how to do this.
            I post, in a previous message, a question about adding complex SOAP header (for Digest authentication), but still no reply (yet).

            Thanks for your reply,
            Cristy.