1 Reply Latest reply on May 19, 2010 3:38 AM by ronnylovtangen

    Experts Help!! Fiendish BlazeDS / Single Sign-on (NTLM) problem

    Milky Jo


      I've been tearing my hair out for a month with this problem - any help would be most gratefully appreciated!


      I need to get a flex app working with single-signon on the windows platform.

      I want to grab the windows username and domain from the browser without having users enter by hand.

      I will then authenticate against my own repository tables accessed via remote objects (blazeds + spring flex + spring + hibernate)


      I have a servlet that uses NTLM authentication challenge response. The servlet works on its own returning usename and domain.

      See below for servlet code


      HOWEVER - no matter how i call the servlet from flex it seems to totally screw up blazeds. No further remote object calls are possible.

      The same remote call works before but not after the servlet has been called. Its driving me insane!!!


      I suspect the problem is related to how the single initial call to the servlet from Flex results in a further two executions of the servlet.

      I assume Internet Explorer is initiating further calls.


      I've tried calling it in the following ways...

      - HTTPServce with URL

      - HTTPServive with blaze destination

      - From within actionscript

      - From MXML

      - From a flex module

      - from the javascript wrapper using XMLHttpRequest and flashvars

      - With one trouser leg rolled up and my finger in my ear


      Every single time it stops any further remote object calls from working they get as far as

      [BlazeDS][DEBUG] FlexSession created with id 'ADF15BED993AD562EEA9249EE6B33CED' for an Http-based client connection.

      [BlazeDS][DEBUG] Deserializing AMF/HTTP request


      but know further.

      Clever people please help - before i blow my brains out 


      Thanks in advance