Hi, I'm writing an App Engine application that interfaces with my corporate SharePoint Server and needs to authenticate using NTLM Authentication (also known as Integrated Windows Authentication).
I'm using Apache HttpClient 4.1.3 because it supports NTLM authentication out of the box. You need to implement a custom ClientConnectionManager and ManagedClientConnection because some of the classes used internally are not in the AppEngine JRE Class White List, but found a couple of implementations in internet so no probs here. I eventually have it working on my local AppEngine Development server but to my surprise it won't work on the production AppEngine. After many investigations I found that NTLM Authentication needs a persistent connection in order to make a handshake consisting in exchanging 3 messages in 2 HTTP requests. Those 2 HTTP requests MUST be done using the same connection (persistent connection), if not the server will refuse to authenticate. It seems the URLFetchService uses different connections for each request and there is no way of keeping the connection open. The same applies if you're using a URLConnection ... as soon as you receive a response you cannot send more data up the connection. Does anybody have managed to do NTLM authentication in AppEngine? Is there anyway to have a persistent connection? If any AppEngine developer from Google sees this ... please, provide support to persistent connections! +1 Thanks Juan -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
