KB-2316 Emails fail to send with "535 Authentication Credentials Invalid"

Ryan Good — Tue, 30 Jul 2024 22:13:15 GMT

Current Revision posted to Appian Knowledge Base by Ryan Good on 7/30/2024 10:13:15 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send.

The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

The SMTP server is unable to authenticate email send requests coming from Appian due to invalid provided credentials. This can be the result of a typo, but more commonly is the result of specifying AWS credentials instead of the proper SMTP credentials when configuring Appian to use an SMTP server.

More information about the differences between these types of credentials can be found here.

Guidance on generating AWS SES SMTP credentials can be found here.

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

After making these changes, restart the application server for the changes to go into effect.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: July 2024

Tags: email, authentication, smtp, infrastructure

KB-2316 Emails fail to send with "535 Authentication Credentials Invalid"

Ryan Good — Tue, 30 Jul 2024 22:12:16 GMT

Revision 14 posted to Appian Knowledge Base by Ryan Good on 7/30/2024 10:12:16 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send.

The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here.

Guidance on generating AWS SES SMTP credentials can be found here.

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

After making these changes, restart the application server for the changes to go into effect.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: July 2024

Tags: email, authentication, smtp, infrastructure

[DRAFT SUPP-172] Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Tue, 30 Jul 2024 20:08:41 GMT

Revision 13 posted to Appian Knowledge Base by dan.endean on 7/30/2024 8:08:41 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send.

The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here.

Guidance on generating AWS SES SMTP credentials can be found here.

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

After making these changes, restart the application server for the changes to go into effect.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: July 2024

Tags: email, authentication, smtp, infrastructure

[DRAFT SUPP-172] Emails fail to send with "535 Authentication Credentials Invalid"

Ryan Good — Tue, 30 Jul 2024 16:46:38 GMT

Revision 12 posted to Appian Knowledge Base by Ryan Good on 7/30/2024 4:46:38 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send.

The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here.

Guidance on generating AWS SES SMTP credentials can be found here.

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: July 2024

Tags: email, authentication, smtp, infrastructure

[DRAFT SUPP-172] Emails fail to send with "535 Authentication Credentials Invalid"

Ryan Good — Tue, 30 Jul 2024 16:45:31 GMT

Revision 11 posted to Appian Knowledge Base by Ryan Good on 7/30/2024 4:45:31 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here.

Guidance on generating AWS SES SMTP credentials can be found here.

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: July 2024

Tags: email, authentication, smtp, infrastructure

[DRAFT SUPP-172] Emails fail to send with "535 Authentication Credentials Invalid"

pauline.delacruz — Wed, 24 Jul 2024 16:46:47 GMT

Revision 10 posted to Appian Knowledge Base by pauline.delacruz on 7/24/2024 4:46:47 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here.

Guidance on generating AWS SES SMTP credentials can be found here.

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: July 2024

Tags: email, authentication, smtp, infrastructure

[DRAFT SUPP-172] Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:52:52 GMT

Revision 9 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:52:52 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here: https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-credentials.html

Guidance on generating AWS SES SMTP credentials can be found here: https://docs.aws.amazon.com/ses/latest/dg/smtp-credentials.html

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

[DRAFT SUPP-172] Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:52:20 GMT

Revision 8 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:52:20 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here: https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-credentials.html

Guidance on generating AWS SES SMTP credentials can be found here: https://docs.aws.amazon.com/ses/latest/dg/smtp-credentials.html

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:49:41 GMT

Revision 7 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:49:41 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server fail to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here: https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-credentials.html

Guidance on generating AWS SES SMTP credentials can be found here: https://docs.aws.amazon.com/ses/latest/dg/smtp-credentials.html

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:49:13 GMT

Revision 6 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:49:13 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server are failing to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
    at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
    at jakarta.mail.Service.connect(Service.java:342)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
    at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
    at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
    at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
    at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
    at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
    at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
    at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

More information about the differences between these types of credentials can be found here: https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-credentials.html

Guidance on generating AWS SES SMTP credentials can be found here: https://docs.aws.amazon.com/ses/latest/dg/smtp-credentials.html

Action

Ensure that the following properties are set to the correct values that correspond to your AWS SES SMTP credentials:

conf.mailhandler.mail.user=<AWS SES SMTP Username> (in <APPIAN_HOME>/conf/custom.properties)
conf.password.SMTP=<AWS SES SMTP Password> (in <APPIAN_HOME>/conf/passwords.properties)

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:33:16 GMT

Revision 5 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:33:16 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server are failing to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
 at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
 at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
 at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
 at jakarta.mail.Service.connect(Service.java:342)
 at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
 at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
 at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
 at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
 at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
 at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
 at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
 at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
 at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
 at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
 at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
 at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:32:49 GMT

Revision 4 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:32:49 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server are failing to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
at jakarta.mail.Service.connect(Service.java:342)
at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:32:21 GMT

Revision 3 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:32:21 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server are failing to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
at jakarta.mail.Service.connect(Service.java:342)
at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:32:08 GMT

Revision 2 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:32:08 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server are failing to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid

at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)

at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)

at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)

at jakarta.mail.Service.connect(Service.java:342)

at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)

at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)

at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)

at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)

at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)

at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)

at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)

at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)

at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)

at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)

at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)

at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024

Emails fail to send with "535 Authentication Credentials Invalid"

dan.endean — Wed, 26 Jun 2024 20:31:37 GMT

Revision 1 posted to Appian Knowledge Base by dan.endean on 6/26/2024 8:31:37 PM

Symptoms

Emails from a self-managed Appian environment that uses AWS SES for its SMTP server are failing to send. The following error trace is observed in tomcat-stdOut.log:

jakarta.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid
	at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
	at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
	at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
	at jakarta.mail.Service.connect(Service.java:342)
	at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:395)
	at com.appiancorp.ap2.mail.Mail.sendMessage(Mail.java:285)
	at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:155)
	at com.appiancorp.ap2.mail.Emailer.send(Emailer.java:150)
	at com.appiancorp.process.runtime.activities.SendEmailActivity.execute(SendEmailActivity.java:474)
	at com.appiancorp.suiteapi.process.framework.AbstractActivity.perform(AbstractActivity.java:104)
	at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:90)
	at com.appiancorp.process.runtime.framework.LegacyActivityExecutor$2.call(LegacyActivityExecutor.java:87)
	at com.appiancorp.common.ContextClassLoaderSwitcher.runInContext(ContextClassLoaderSwitcher.java:24)
	at com.appiancorp.process.runtime.framework.LegacyActivityExecutor.execute(LegacyActivityExecutor.java:87)
	at com.appiancorp.process.engine.UnattendedJavaActivityRequest.execute(UnattendedJavaActivityRequest.java:88)
	at com.appiancorp.process.engine.UnattendedJavaActivityRequestResponseCreator.getJavaActivityResultResponse

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

Action

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: June 2024