+5Hi,
so in a couple of weeks Google will shut down basic auth for gmail SMTP (Transition from less secure apps to OAuth ).
As this is how we (and probably many other Jamf Pro customers) set up our Jamf Pro in the cloud to send us notification mails, we are now strugeling to find a way for the future.
Has anyone (without an other mail server besides Google) found a solution jet?
Or has anyone heard of OAuth support for Jamf Pro smtp settings?
Kind regards, Matthias
Best answer by jamf-42
and 11.9 is out:
You can now integrate Google-hosted email accounts with Jamf Pro using Google Cloud's Identity and Access Management system. Beginning 30 September 2024, Google will require OAuth 2.0 for third-party apps to access Gmail, meaning that adding Gmail accounts via basic authentication will no longer be supported in Jamf Pro. This feature allows you to integrate a Gmail account with Jamf Pro by authenticating directly through Google via OAuth 2.0, enabling Jamf Pro to securely authenticate when sending email notifications for various actions that take place in your environment.
To access this feature in Jamf Pro, navigate to , and select from the Authentication method pop-up menu.
For more information on integrating an SMTP server, see SMTP Server Integration in the Jamf Pro Documentation.
+17join the JAMF Pro betas... via feedback in your JAMF ID account.. more info there..
+1Hi Matthias,
The transition to OAuth for Gmail SMTP is challenging for Jamf Pro users, as Jamf currently doesn't support OAuth for SMTP settings. Possible solutions include using a third-party SMTP service like SendGrid or Mailgun, setting up a G Suite SMTP relay, or exploring custom OAuth workflows. These options can help maintain email notifications. I recommend testing these alternatives now to ensure a smooth transition. Additionally, keep an eye on Jamf’s updates, as they might introduce OAuth support in the future.
Kind regards,
Karan
+17and 11.9 is out:
You can now integrate Google-hosted email accounts with Jamf Pro using Google Cloud's Identity and Access Management system. Beginning 30 September 2024, Google will require OAuth 2.0 for third-party apps to access Gmail, meaning that adding Gmail accounts via basic authentication will no longer be supported in Jamf Pro. This feature allows you to integrate a Gmail account with Jamf Pro by authenticating directly through Google via OAuth 2.0, enabling Jamf Pro to securely authenticate when sending email notifications for various actions that take place in your environment.
To access this feature in Jamf Pro, navigate to , and select from the Authentication method pop-up menu.
For more information on integrating an SMTP server, see SMTP Server Integration in the Jamf Pro Documentation.
+9Anyone having an issue following this Article to create the unique client ID and client secret in your Google Workspace portal? I can start the process by creating the new project but I don't see the "Product name" field nor where I can select "Web server"!
+1Seems pretty straightforward, but we are getting:
POST https://oauth2.googleapis.com/token
{
"error": "redirect_uri_mismatch",
"error_description": "Bad Request"
}
+14Seems pretty straightforward, but we are getting:
POST https://oauth2.googleapis.com/token
{
"error": "redirect_uri_mismatch",
"error_description": "Bad Request"
}
Hello.
I was at first getting a redirect_uri_mismatch, but noticed I had a typo. Now that is fixed, I can successfully send email on my test server, but NOT on my production server... which has a port number. I am able to enter the email address and password, but then get an error "Unable to add and authenticate email account due to an issue with a token, please try again".
Has anybody got it working with a port number (:8443) as part of your jamf URL?
thank you,
chris
+14Hello.
I was at first getting a redirect_uri_mismatch, but noticed I had a typo. Now that is fixed, I can successfully send email on my test server, but NOT on my production server... which has a port number. I am able to enter the email address and password, but then get an error "Unable to add and authenticate email account due to an issue with a token, please try again".
Has anybody got it working with a port number (:8443) as part of your jamf URL?
thank you,
chris
[update]
I captured a debug log, and it is still a redirect URI issue
{
"error": "redirect_uri_mismatch",
"error_description": "Bad Request"
}
Since it works on my test server but not when I add port number :8443, perhaps this is a Google issue? I started here because anything locally hosted would have the port number so hoped someone had seen this and had a fix.
@user-xhWIUceCkh does your jamf server URL use a port number?
thanks,
chris
+14I had to specifically enable the Gmail permission set in Google OAuth to get this working
Documentation can be found in the following resources:
+1I have followed the SMTP Server Integration / Preparing Google Workspace for Jamf Pro SMTP Integration articles over and over again (as solutions indicate above). We are still having issues setting up SMTP integration with Google OAuth. We have received the following error every time:
+14I have followed the SMTP Server Integration / Preparing Google Workspace for Jamf Pro SMTP Integration articles over and over again (as solutions indicate above). We are still having issues setting up SMTP integration with Google OAuth. We have received the following error every time:
I agree it's not the best experience. But have you opened a Jamf Support Case on this?
+1I agree it's not the best experience. But have you opened a Jamf Support Case on this?
Tried doing that about 6 days ago and no fixes yet from them. Really is a shame - to your point, I wish Jamf would create a better customer experience in integrating with google for SMTP. The fact that a lot of folks were required to turn on "less secure app" and "app password" settings to begin with as primary work arounds was the true problem here in my opinion. Google naturally is attempting to better secure it's platform and removed these options.
+1Updated: I opened a support ticket and validated the issue. The workaround is pretty Mickey Mouse. If you have an issue, open a support ticket because there are items on your side and the backend they have to do.
+7Updated: I opened a support ticket and validated the issue. The workaround is pretty Mickey Mouse. If you have an issue, open a support ticket because there are items on your side and the backend they have to do.
Anyone find a published solution to this and not a "you have to go to support" fix? I am also getting the token error...
+11I am also having trouble with Step 8-9 click the "Add email address via google" button, there isn't enough elaboration on "follow the Google Authentication workflow", because it doesn't work. I sign into Google and then am redirected back to Jamf Pro with nothing changed. I tried a different SMTP account for Google and I get something like "access to Jamf Pro denied". Do we need to ALSO create a Jamf Pro user account matching the email account intended to be used for SMTP (this was not required before with Basic Authentication / password).
Agree, not sure why it is so difficult for Jamf to implement a proper Google OAuth sign-in under the SMTP settings, like exists for many other apps and services.
+11I am also having trouble with Step 8-9 click the "Add email address via google" button, there isn't enough elaboration on "follow the Google Authentication workflow", because it doesn't work. I sign into Google and then am redirected back to Jamf Pro with nothing changed. I tried a different SMTP account for Google and I get something like "access to Jamf Pro denied". Do we need to ALSO create a Jamf Pro user account matching the email account intended to be used for SMTP (this was not required before with Basic Authentication / password).
Agree, not sure why it is so difficult for Jamf to implement a proper Google OAuth sign-in under the SMTP settings, like exists for many other apps and services.
I was able to successfully add the Google Email Address in Step 8-9 by being logged into Jamf Cloud in a private browser window using the the ?failover URL and a non-SSO account (we have SSO enabled and use it generally for our Jamf Server accounts.) However, after adding the Google Email with the Authenticated checkmark showing, and Saving the SMTP configuration, I was unable to send a Test email. I get "Error sending message. Ensure you can connect to the SMTP server" Waiting for Support Ticket response, in the meantime I had to change the SMTP method back to Basic Credentials (which will no longer work for our Google Workspace in about a week!)
+6Hi all,
For anyone here, or people from the future... I had a new Jamf Pro instance to setup with SMTP and started to go down the Google OAuth road, but after reading of even people's recent issues configuring it I thought I'd remind folks of the other Google option (besides SMTP relay) that should continue to be available and is relatively quick and painless to setup: App Passwords.
In a nutshell, they allow clients to authenticate as 2FA enabled Google users with basic user/pass, like Jamf Pro's SMTP, by generating a unique password that can only be used with that client ongoing.
I wrote up the full instructions in a reply to this SMTP related post a while back...
https://community.jamf.com/t5/jamf-pro/smtp-relay-with-google-workspace/m-p/288444#M257870
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.