Extension talk:NTLMActiveDirectory

Previous page history was archived for backup purposes at Extension talk:NTLMActiveDirectory/LQT Archive 1 on 2015-07-10.

After a long struggle, I was able to get the extension active in my environment, however I am now unable to upload files at all, receiving the "Sorry! We could not process your edit due to a loss of session data." warning when uploading any file.

Uploads directly from the target server work fine using the localhost address. I do not appear to be getting any problems with any other forms of edit, just file uploads, so I'm wondering if there is any known issue. The identified PHP session folder is populating with files.

Are there any other clues I should be looking for?

Running Windows Server 2012, IIS 8.5, MySQL, PHP 5.5.29, current mediawiki and NTLMActiveDirectory extension enabled.

Did a lot more tinkering and was able to resolve the session data, but I am still unable to get file uploads to work via HTTP remote versus localhost where they work fine.

Can you please let me know how have you resolved the session data issue

Can you let me know how the session data has been resolved

1.27 broke Auth_remoteuser. Did it break this too?

I can't get this working with 1.27 on our system either.

Addition of the extension does not look like a complicated task but apparently I see that DCOM queries against the Active Directory the extension uses fail. I use Windows Server 2012 with PHP 5.6, and the Active Directory services are located at another server.

The situation looks similar to the Double-Hop problem: the query fails for an authentication request coming from a remote client. If I use browser on the same server, the AD queries succeed. Nevertheless, there is something odd anyway: I built a simple ASP page performing the same requests against the AD, and this works for both local and remote clients.

Has someone faced this problem? Any ideas how this can be resolved? Am I missing something in use of the extension? I can think about building a local ASP-based web service to perform AD queries for the extension (modifying the extension to use corresponding web requests instead of direct AD querying) but this starts sound a bit insane.