-
Bug
-
Resolution: Fixed
-
Low
-
5.13.1, 5.14.1, 5.15.0, 5.15.1, 5.15.2
-
3
-
Severity 3 - Minor
-
3
-
Issue Summary
Starting in JSM 5.14.1 it is no longer possible to configure an email channel, with Microsoft as the service provider, while using the "SECURE_POP" protocol. For an email channel after authorizing the connection the status shows as "Failure" and the connectivity log shows the error "Protocol error, Connection is closed, 10'.
Using the same configuration in JSM 5.14.0 and below the connection is successful.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Create an outgoing application link for OAuth authentication, for a Microsoft service provider, where the https://outlook.office.com/POP.AccessAsUser.All scope has been added.
- Create an email requests channel in a service project and set the protocol being used to "SECURE_POP" and the authentication method to OAuth.
- Attempt to save the configuration which will prompt you to authorize the connection in 0365.
Expected Results
After following the configuration outlined in Integrating OAuth 2.0 for Microsoft Accounts on Jira the connection should be successful and the email channel should become active.
Actual Results
The connection status shows as "Failure" and checking the connectivity logs for the email channel in question shows 'Protocol error, Connection is closed, 10'
The below exception is thrown in the atlassian-jira-incoming-mail.log file:
2024-03-28 17:46:17,704+0000 ERROR [] Caesium-1-4 ServiceRunner Messaging Error when MailPullerWorker pulls emails from jiratest702@outlook.com: Protocol error. Connection is closed. 10 javax.mail.AuthenticationFailedException: Protocol error. Connection is closed. 10 at com.sun.mail.pop3.POP3Store.protocolConnect(POP3Store.java:193) [jakarta.mail-1.6.7.jar:1.6.7] at javax.mail.Service.connect(Service.java:342) [jakarta.mail-api-1.6.7.jar:1.6.7] at javax.mail.Service.connect(Service.java:222) [jakarta.mail-api-1.6.7.jar:1.6.7] at javax.mail.Service.connect(Service.java:243) [jakarta.mail-api-1.6.7.jar:1.6.7] at com.atlassian.jira.internal.mail.processor.feature.puller.MailPullerWorker.pullEmailForConnection(MailPullerWorker.java:174) [jira-email-processor-plugin-15.14.1-REL-0002.jar:?] at com.atlassian.jira.internal.mail.processor.feature.puller.MailPullerWorker.pullMailFromAllValidChannels(MailPullerWorker.java:107) [jira-email-processor-plugin-15.14.1-REL-0002.jar:?] at com.atlassian.jira.internal.mail.processor.feature.puller.MailPullerService.run(MailPullerService.java:33) [jira-email-processor-plugin-15.14.1-REL-0002.jar:?] at com.atlassian.jira.internal.mail.processor.services.MailPullerExecutor.run(MailPullerExecutor.java:29) [jira-email-processor-plugin-15.14.1-REL-0002.jar:?] at com.atlassian.jira.internal.mail.processor.services.AbstractMailExecutor.execute(AbstractMailExecutor.java:45) [jira-email-processor-plugin-15.14.1-REL-0002.jar:?] at com.atlassian.jira.internal.mail.processor.services.MailJobRunner.runJob(MailJobRunner.java:35) [jira-email-processor-plugin-15.14.1-REL-0002.jar:?] at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134) [atlassian-scheduler-core-4.1.0.jar:?] at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106) [atlassian-scheduler-core-4.1.0.jar:?] at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90) [atlassian-scheduler-core-4.1.0.jar:?] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:500) [atlassian-scheduler-caesium-3.1.4.jar:?] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:495) [atlassian-scheduler-caesium-3.1.4.jar:?] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:519) [atlassian-scheduler-caesium-3.1.4.jar:?] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:415) [atlassian-scheduler-caesium-3.1.4.jar:?] at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66) [atlassian-scheduler-caesium-3.1.4.jar:?] at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60) [atlassian-scheduler-caesium-3.1.4.jar:?] at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35) [atlassian-scheduler-caesium-3.1.4.jar:?] at java.base/java.lang.Thread.run(Unknown Source) [?:?]
Workaround
Currently, there is no known workaround for this behavior when using SECURE_POP protocol. A workaround will be added here when available. Using SECURE_IMAP is confirmed to allow for Jira to successfully connect to the mailbox.
- mentioned in
-
Page Loading...