Skip to main content

After Google announced they would not be allowing basic credentials for SMTP, we are struggling to get the Google OAuth to work. We have followed the steps below and still not have had any luck. It keeps giving us this error but we have tried multiple URLs for the failover and it is not working. Any suggestions?

References: 

SMTP Server Integrations

Preparing a Google Workspace for Jamf Pro 
Jamf Pro SMTP Walkthrough

 

I presented on configuring Jamf Pro SMTP server settings for OAuth with both Microsoft and Google at last month's University of Utah MacAdmins meeting. You might find it useful.

https://stream.lib.utah.edu/index.php?c=details&id=13663

The redirect URL you want to use is the one you'd see when viewing your own Jamf Pro server's SMTP server settings. For example: "https://talkingmoose.jamfcloud.com/view/settings/system-settings/smtp-server".


I presented on configuring Jamf Pro SMTP server settings for OAuth with both Microsoft and Google at last month's University of Utah MacAdmins meeting. You might find it useful.

https://stream.lib.utah.edu/index.php?c=details&id=13663

The redirect URL you want to use is the one you'd see when viewing your own Jamf Pro server's SMTP server settings. For example: "https://talkingmoose.jamfcloud.com/view/settings/system-settings/smtp-server".


With or without the port #? Assuming without?


I presented on configuring Jamf Pro SMTP server settings for OAuth with both Microsoft and Google at last month's University of Utah MacAdmins meeting. You might find it useful.

https://stream.lib.utah.edu/index.php?c=details&id=13663

The redirect URL you want to use is the one you'd see when viewing your own Jamf Pro server's SMTP server settings. For example: "https://talkingmoose.jamfcloud.com/view/settings/system-settings/smtp-server".


I tried doing that and am still getting the error about being unable to add an account. I followed exactly what your presentation had as well.


With or without the port #? Assuming without?


If something other than 443, such as an on-prem installation using port 8443, you’ll need to include the port. Jamf Cloud uses port 443 and therefore doesn’t need it.


If something other than 443, such as an on-prem installation using port 8443, you’ll need to include the port. Jamf Cloud uses port 443 and therefore doesn’t need it.


Our server is cloud-hosted but still says 8443.


You’ll need to include the 8443. Copy the URL as I demonstrated. That’s what you need.


We are cloud based and needed to include the 8443 for it to work.


You’ll need to include the 8443. Copy the URL as I demonstrated. That’s what you need.


I added the 8443 and it still is giving me the error listed above. Sounds like it is a google problem with the token