You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2020. It is now read-only.
What version of fleet are you using (fleet version --full)?
fleet - version 2.4.0
branch: master
revision: 70c6f5bd7d8a337a97f7702ee17088e74722896f
build date: 2019-11-12T23:10:49Z
build user: zwass
go version: go1.12.8
What operating system are you using?
$uname -a
$Linux fleet-1 5.0.0-1026-gcp #27~18.04.1-Ubuntu SMP Fri Nov 15 07:40:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
What did you do?
Created a new GSuite service account to use with Fleet's need for email. the account was something like [email protected], and less secure app access was enabled on the email account side.
I entered in all information, having verified it as correct via logging in to a web browser, but I was unable to save successfully.
What did you expect to see?
I expected the information to save correctly and for SMTP to show as configured. Unfortunately, I kept getting an error.
What did you see instead?
sending mail: client auth error: 535 5.7.8 Username and Password not accepted. Learn more at 5.7.8 https://support.google.com/mail/?p=BadCredentials <random string> - gsmtp
After much tearing of hair and a complete lack of any other error messages that I could find, I created another user acct, [email protected], and set exactly the same password to eliminate any possibility of special characters being the issue. After enabling less secure app access in GSuite, I was greeted with success/"SMTP Configured" upon saving the non-hyphenated credentials in the Fleet Dashboard.
Gmail regular does not allow for the creation of usernames with hyphens, only alphanums and periods. GSuite, however, does allow for the creation of email addresses with hyphens, and it would appear that Kolide Fleet does not support that. Is this a function in fleet that needs to be updated, or an upstream Go dependency, or?
it is working with the non-hyphenated email account, but this breaks our naming scheme, and makes clarity and auditing more difficult. Please update/add support for this in email addresses if possible!
The text was updated successfully, but these errors were encountered:
What version of
fleet
are you using (fleet version --full
)?What operating system are you using?
What did you do?
Created a new GSuite service account to use with Fleet's need for email. the account was something like [email protected], and less secure app access was enabled on the email account side.
I entered in all information, having verified it as correct via logging in to a web browser, but I was unable to save successfully.
What did you expect to see?
I expected the information to save correctly and for SMTP to show as configured. Unfortunately, I kept getting an error.
What did you see instead?
sending mail: client auth error: 535 5.7.8 Username and Password not accepted. Learn more at 5.7.8 https://support.google.com/mail/?p=BadCredentials <random string> - gsmtp
After much tearing of hair and a complete lack of any other error messages that I could find, I created another user acct, [email protected], and set exactly the same password to eliminate any possibility of special characters being the issue. After enabling less secure app access in GSuite, I was greeted with success/"SMTP Configured" upon saving the non-hyphenated credentials in the Fleet Dashboard.
Gmail regular does not allow for the creation of usernames with hyphens, only alphanums and periods. GSuite, however, does allow for the creation of email addresses with hyphens, and it would appear that Kolide Fleet does not support that. Is this a function in fleet that needs to be updated, or an upstream Go dependency, or?
it is working with the non-hyphenated email account, but this breaks our naming scheme, and makes clarity and auditing more difficult. Please update/add support for this in email addresses if possible!
The text was updated successfully, but these errors were encountered: