Itop mail to ticket automation.

[Peter Mwihaki]

Hi there.
I have this problem trying to create an OAuth 2.0 Mail Inbox (Azure). All notifications seems to be working okay but I can not seem to get OAuth 2.0 Mail Inbox to work.! It keeps on loading. Already enabled ssl in the configuration file. Nothing in debug trace (imap options)
I checked the error.log and below is a screenshot of the error. Anyone with an idea of what i could be missing?

[Jeffrey Bostoen]

Perhaps check you're also using a modern OpenSSL version on your web server?

[Peter Mwihaki]

Hi Jeffrey.
Thank you fro the reply. I am currently using OpenSSL 1.1.1f . Can this be the cause of this error? If it is can you kindly suggest a way to handle this situation.

[Jeffrey Bostoen]

Mind that OpenSSL 1.1.1 is officially end of life: https://www.openssl.org/blog/blog/2023/03/28/1.1.1-EOL/index.html

[Peter Mwihaki]

Hi Jeffrey.
I am using Ubuntu 20.04 seems to be no upgrade for OpenSSL 1.1.1f. It is already the latest.

Tue Jul 09 10:15:42.030829 2024] [php7:warn] [pid 625680] [client 41.215.0.150:52435] PHP Warning:  fwrite(): SSL operation failed with code 1. OpenSSL Error messages:\nerror:1420C0CF:SSL routines:ssl_write_internal:protocol is shutdown in /var/www/html/itop/env-production/combodo-oauth-email-synchro/src/Service/IMAPOAuthLogin.php on line 162, referer: https://x.x.x.x/itop/pages/UI.php?operation=details&class=MailInboxOAuth&id=9&

I have gone through hundreds of posts and can't seem to find anyone with OpenSSL error on an Oauth Mail inbox. Any suggestions will be highly appreciated.

[Peter Mwihaki]

Also I am using a self-signed certificate. In config file -imap-options.

'imap_options' => array (
          0 => 'imap',
          1 => 'ssl',
          2 => 'novalidate-cert',
        ),

[Jeffrey Bostoen]

You have verified if your web server can indeed connect to the configured mail host, on the correct port?

https://www.google.com/search?q=openssl+%22protocol+is+shutdown%22&
This kind of error is raised when the SSL wrapper tries to write to a closed TCP connection. It is usually related to connection problems, firewalls or SSL interception.