I think it's going to be hard to answer this question definitively the way it is written.

The filehandle problem is hard to ignore since its warnings-spew occupies such a large portion of your post. But the most serious problem is this one:

2016.11.15,14:23:36,ERROR,GENERAL,Script died: Can't locate LWP/Authen
+/Session.pm in @INC (@INC contains: G:/development/HiCHperfpkg/bin\..
+\lib\modules G:/development/HiCHperfpkg/bin C:/Perl64/site/lib C:/Per
+l64/lib .) at (eval 72) line 2.
[download]

Your problem description states that you do not get this message when you test with a wrong URL, but you do get it if you test with the real target URL. It seems likely that the issue manifests itself with those criteria because the LWP::Authen::Session module is being dynamically loaded, on demand, when authentication is needed. If you hit the wrong URL, no authentication is needed, so the module never gets loaded. As soon as you point to the correct URL, authentication is needed, and you get your error message.

So it seems you do not have LWP::Authen::Session installed on your system, or at least not in a place where Perl can find it. The line of code where that module is loaded was not included in your sample code, either. We cannot really look to see the precise problem because the code that is causing the problem happens in a place outside of the code you showed us.

I went to http://search.cpan.org and the interwebs themselves looking for mention of LWP::Authen::Session and came up empty handed. I even grepped through the code of other LWP::* modules that seemed like they might be relevant to find mention of LWP::Authen::Session, and didn't find anything. I'm reluctant to mention this, because as soon as I do (or within a few minutes) someone will find it and expose the inadequacies in my searching. But I'm going with the assumption that LWP::Authen::Session must be an in-house module, not available on CPAN. If that's the case, you'll have to talk to someone at your shop and find out how to get it installed.

Hi Dave,

it works without problem when the credentials are correct. So there must be some authentication working.

When I comment out the line ..

 
    my $req = HTTP::Request->new;
    $req->header('content-type' => 'application/json');
    $req->header('accept' => 'application/json');
    $req->method($par_httpmethod);
    #$req->authorization_basic($par_user,$par_pass);
    $req->uri($url_string);

        my $response = $ua->request($req);
[download]

.. I get the same error message.

regards
de Michi

I agree with davido - there is no evidence which I can find of any LWP::Authen::Session module publicly available anywhere. You (or your programmers) have likely written this module and plugged it into the existing HTTP client framework. This is therefore a problem for you and your organisation to solve internally.

Here is an SSCCE which shows how HTTP Basic Auth failures are properly handled in the modules available on CPAN:

#!/usr/bin/env perl 
use strict;
use warnings;

use LWP::UserAgent;
use Test::More tests => 1;

my $ua = LWP::UserAgent->new ();
my $res = $ua->get ('https://pause.perl.org/pause/authenquery');
is ($res->status_line, '401 Unauthorized', 'Request returns a valid 40
+1');
[download]

All,

I found the code example for authorization_basic somewhere on perlmonks ...

http://www.perlmonks.org/?node_id=148451

or

http://www.perlmonks.org/bare/?node_id=313478

and also on stackoverflow.

http://stackoverflow.com/questions/8203964/lwpuseragent-http-basic-authentication

or here https://perlmaven.com/basic-authentication-with-lwp-useragent-and-http-request-common

So this is nothing internally.

regards, de michi

There is a lot of misinformation going on in this thread. Looking at the source of LWP::UserAgent, I see the following code:

sub request {
...
    {
    my $proxy = ($code == &HTTP::Status::RC_PROXY_AUTHENTICATION_REQUI
+RED);
    my $ch_header = $proxy || $request->method eq 'CONNECT'
        ?  "Proxy-Authenticate" : "WWW-Authenticate";
    my @challenge = $response->header($ch_header);
    unless (@challenge) {
        $response->header("Client-Warning" => 
                  "Missing Authenticate header");
        return $response;
    }

    require HTTP::Headers::Util;

CHALLENGE: for my $challenge (@challenge) {
        $challenge =~ tr/,/;/;  # "," is used to separate auth-params!
+!
        ($challenge) = HTTP::Headers::Util::split_header_words($challe
+nge);
        my $scheme = shift(@$challenge);
        shift(@$challenge); # no value
        $challenge = { @$challenge };  # make rest into a hash

        unless ($scheme =~ /^([a-z]+(?:-[a-z]+)*)$/) {
        $response->header("Client-Warning" => 
                  "Bad authentication scheme '$scheme'");
        return $response;
        }
        $scheme = $1;  # untainted now
        my $class = "LWP::Authen::\u$scheme";
        $class =~ s/-/_/g;

        no strict 'refs';
        unless (%{"$class\::"}) {
        # try to load it
        eval "require $class";
        if ($@) {
            if ($@ =~ /^Can\'t locate/) {
            $response->header("Client-Warning" =>
                      "Unsupported authentication scheme '$scheme'");
            }
            else {
            $response->header("Client-Warning" => $@);
            }
            next CHALLENGE;
        }
        }
...
[download]

So, HTTP::Request will attempt to load a module LWP::Authen::$scheme when the server responds with a WWW-Authenticate header, which it does if your credentials are wrong.

Contrary to your expectation, it doesn't seem to respond with WWW-Authenticate: Basic but with WWW-Authenticate: Session, which makes LWP::UserAgent fail with the above error message. Maybe consider looking at what actually goes over the wire, what the actual response of the server is in your case, and maybe then decide to either fake LWP::Authen::Session as identical to LWP::Authen::Basic or to implement it yourself or to raise a bug against LWP::UserAgent.