Re: No socket creation during request

--0000000000001f0a800612e2ebde
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi team,

Sorry I forgot a little more information.
We are able to connect to the sharepoint server through openssl
command(*openssl
s_client connect server:port*).
The request made via the LWP module to the sharepoint-server is through
*TLS-1.2* protocol.

*Perl version being used: perl-5.18.2*

Thanks,
N G Hemanth Kumar

On Tue, Mar 5, 2024 at 10:29=E2=80=AFAM N G Hemanth Kumar <
[email protected]> wrote:

> Hi team,
>
> Hope you are doing well. We have NTLM Sharepoint application configured i=
n
> our application. The library we are using to support the authentication
> operation/feature is *LWP::Authen::Ntlm and Net::SSL*. The authentication
> flow is similar to what is posted in the page=E2=80=99s
> <https://metacpan.org/pod/LWP::Authen::Ntlm> synopsis. It was working
> fine with apache2-2.4.51(without tls1.3) and *openssl-1.0.2p*.
>
> But recently we upgraded the apache2 library to support tls1.3(with
> *openssl-1.1.1d*). After this upgrade, the app is not able to make a
> socket connection to the sharepoint server. When debugged further - it
> wasn't able to create an ssl-socket using *Crypt::SSLeay::Conn->new *in
> *Net::SSL(v2.85)* module.
>
> Could you please let us know what might be the possible reasons for this
> issue and what are the possible ways to resolve this issue?
>
> Apache2 mod-perl : *apache2-mod_perl-2.0.8-13.5.1.x86_64*
> LWP based modules :
> *perl-libwww-perl-6.05, perl-LWP-MediaTypes-6.02, perl-LWP-Protocol-https=
-6.04, perl-IO-Socket-SSL-2.052-4.3.1, perl-Crypt-SSLeay-0.64-3.57, perl-NT=
LM-1.09-1.1, perl-Net-HTTP-6.06-5.2, perl-Net-SSLeay-1.64-3.2.*
>
>
> Thanks,
> N G Hemanth Kumar
>

--0000000000001f0a800612e2ebde
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi team,<div><br><div>Sorry I forgot a little more informa=
tion.=C2=A0<br>We are able to connect to the sharepoint server through open=
ssl command(<b>openssl s_client connect server:port</b>).<br>The request ma=
de via the LWP module to the sharepoint-server is through <b>TLS-1.2</b> pr=
otocol.<br><br><b>Perl version being used:=C2=A0perl-5.18.2</b></div></div>=
<div><b><br></b></div><div>Thanks,</div><div>N G Hemanth Kumar</div></div><=
br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue,=
 Mar 5, 2024 at 10:29=E2=80=AFAM N G Hemanth Kumar &lt;<a href=3D"mailto:he=
[email protected]">[email protected]</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>H=
i team,<br><br>Hope you are doing well. We have NTLM Sharepoint application=
 configured in our application. The library we are using to support the aut=
hentication operation/feature is <b>LWP::Authen::Ntlm and Net::SSL</b>. The=
 authentication flow is similar to what is posted in the=C2=A0<a href=3D"ht=
tps://metacpan.org/pod/LWP::Authen::Ntlm" target=3D"_blank">page=E2=80=99s<=
/a>=C2=A0synopsis. It was working fine with apache2-2.4.51(without tls1.3) =
and <b>openssl-1.0.2p</b>.<br><br>But recently we upgraded the apache2 libr=
ary to support tls1.3(with <b>openssl-1.1.1d</b>). After this upgrade, the =
app is not able to make a socket connection to the sharepoint server. When =
debugged further - it wasn&#39;t able to create an ssl-socket using=C2=A0<b=
>Crypt::SSLeay::Conn-&gt;new </b>in <b>Net::SSL(v2.85)</b> module.</div><di=
v><br>Could you please let us know what might be the possible reasons for t=
his issue and what are the possible ways to resolve=C2=A0this issue?<br><br=
>Apache2 mod-perl : <b>apache2-mod_perl-2.0.8-13.5.1.x86_64</b><br>LWP base=
d modules :=C2=A0<b>perl-libwww-perl-6.05,=C2=A0perl-LWP-MediaTypes-6.02,=
=C2=A0perl-LWP-Protocol-https-6.04,=C2=A0perl-IO-Socket-SSL-2.052-4.3.1,=C2=
=A0perl-Crypt-SSLeay-0.64-3.57,=C2=A0perl-NTLM-1.09-1.1,=C2=A0perl-Net-HTTP=
-6.06-5.2,=C2=A0perl-Net-SSLeay-1.64-3.2.</b></div><div><br><br>Thanks,<br>=
N G Hemanth Kumar<br></div></div>
</blockquote></div>

--0000000000001f0a800612e2ebde--