in reply to Re: Authorizing with NTLM - Problem Domain
in thread Authorizing with NTLM - Problem Domain

Hey

not really... I mean, I alreday tried it like this:

$ua->credentials($Options->{'domain'}, '', $Options->{'user'}, $Options->{'password'});

and this:

ntlm_domain($Options->{'domain'}); ntlm_user($Options->{'user'}); ntlm_password($Options->{'password'}); my $Authorization = Authen::NTLM::ntlm();

Replies are listed 'Best First'.
Re^3: Authorizing with NTLM - Problem Domain
by haukex (Archbishop) on May 18, 2018 at 08:47 UTC

    I don't know anything about Authen::NTLM, and the docs aren't really helpful here, but the thread linked to in the AM post shows the method being used as $ua->credentials('10.1.1.1:80', '', 'myDomain\\user', 'password');. What is your $Options->{'user'}, have you tried my $Options = { user => 'Domain\\UsernameIsHere', ...?

      I have also tried this:

      { my $Options = user => 'Domain\\UsernameIsHere', password => "***********", domain => 'ServerAddressIsHere.com/', timeout => 30, protocol => "https", AuthMethod => "NTLM", ##BrowserAgent => "MSIE 6.0; Windows NT 5.0", RequestMethod => "GET", ##DataDir => "/tmp", };

      But this would also not lead any further

      Error message is:

      ERROR: Can not dump data from http://ServerAddressIsHere.com/mbSDKServ +ice/MsgSDK.asmx/RunQuery?queryName=QueryNameIsHere Returned code: 401 (401 Unauthorized)

        Then I'm out of ideas (and time) for the moment, sorry :-( Best I can do is suggest to have a look at the issue tracker, at least one of the tickets has some discussion in it, and to trace a successful request with Wireshark and compare it to a failed request and see what the difference is.