Open dspang opened 1 month ago
Hello @dspang , did you encode the secret in base64 like mentioned in the doc ?
Hello @dspang , did you encode the secret in base64 like mentioned in the doc ?
I did. This is the conversion script I used:
I have also successfully decoded from base64 manually and within Kestra. Bloody strange.
Ok thanks for the update Could be the same issue as https://github.com/kestra-io/plugin-fs/issues/156
Expected Behavior
The plugin io.kestra.plugin.notifications.mail.MailSend should properly decode my username and password which are stored as secrets via a .env_encoded file.
I have validated that my credentials are being ingested in two ways:
1 - Ran the same failing workflow with hard coded credentials instead of having it decode the secrets but added
{{ secret('EMAIL_USERNAME') }}
and{{ secret('EMAIL_PASSWORD') }}
into the body of the email. This email sent successfully and had the properly decoded credentials in the email body as expected.2 - Ran a separate flow to log the credentials after decoding. While the code listed below does appear to have properly decoded the values and logged them, I am unable to verify with certainty as the result is masked.
Result:
Actual Behaviour
For the send_email error handler listed in the example flow below, a "535 Authentication credentials invalid" error is thrown.
Steps To Reproduce
Environment: Docker Desktop for Windows 11 with a Kestra instance on the latest build backed by a Postgres instance which are both spun up via Docker Compose.
Config: .env_encoded file in the following format.
Run the flow listed in the example flow below.
Receive error "535 Authentication credentials invalid."
Environment Information
Example flow