SSLHandshakeException error when IMAPS protocol is configured for Approval Email Server in RSA Governance & Lifecycle
Last Modified: 2023-10-06
Article Number
Applies To
Issue
javax.mail.MessagingException: Could not connect to message store for imaps://username@imaps-server.hostname:993; nested exception is: javax.mail.MessagingException: Remote host terminated the handshake; nested exception is: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake at com.aveksa.server.email.common.EmailUtils.connectToMailStore(EmailUtils.java:651) at com.aveksa.server.email.mailboxmonitor.MailboxMonitorThread.checkForMail(MailboxMonitorThread.java:178) at com.aveksa.server.email.mailboxmonitor.MailboxMonitorThread.run(MailboxMonitorThread.java:46) Caused by: javax.mail.MessagingException: Remote host terminated the handshake; nested exception is: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:670) at javax.mail.Service.connect(Service.java:295) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at com.aveksa.server.email.common.EmailUtils.connectToMailStore(EmailUtils.java:625) ... 2 more Caused by: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake at com.ibm.jsse2.bj.a(bj.java:18) at com.ibm.jsse2.bj.b(bj.java:1) at com.ibm.jsse2.bj.f(bj.java:427) at com.ibm.jsse2.bj.a(bj.java:406) at com.ibm.jsse2.bj.startHandshake(bj.java:160) at com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:549) at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:354) at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:237) at com.sun.mail.iap.Protocol.<init>(Protocol.java:116) at com.sun.mail.imap.protocol.IMAPProtocol.<init>(IMAPProtocol.java:115) at com.sun.mail.imap.IMAPStore.newIMAPProtocol(IMAPStore.java:685) at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:636) ... 6 moreAn inspection of the TCP network traffic capture data shows a connection being attempted using TLSv1.0.
Cause
Resolution
mail.imaps.ssl.protocols=TLSv1.2Note: The JVM argument can be added on the WebSphere console > click Servers > Server types > WebSphere application servers > Select server > select the server used for SecurID Governance & Lifecycle > Configuration tab > select Server Infrastructure > Java and Process Management > Process Definition > Additional Properties > Java Virtual Machine > Generic JVM Arguments.
Related Articles
Failures processing emails in a cluster in RSA Identity Governance & Lifecycle 135Number of Views Impact of missing information on creation of Profiles by Risk Engine 27Number of Views Provisioning e-mails not being sent by RSA Authentication Manager 8.1 28Number of Views What is the impact of a domain migration in RSA Identity Governance and Lifecycle 42Number of Views RSA Identity Governance and Lifecycle Review Details link ($reviewDetailURL) in Reviewer Email gets "The request could not… 78Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?