KevinTheJedi
Not sure what you mean that I still have that with normal gmail. As I stated before, the normal general gmail, as of May 30, 2022, Google no longer supports the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password.
ticket email reply generated with error
cherrie I have normal, free gmail and have access to google cloud console.. just visit the site and sign in..
Got it. Thanks. The google cloud main page wasn't obvious that console is free.
Noticed that my Mailbox setting>protocol field doesn't have the Oauth2 option (only has IMAP and POP). I probably didn't download that plugin when I downloaded the 1.17 files. I downloaded again the 1.17 files with Oauth2, uploaded to server and the protocol field still doesn't have the Oauth2 option.
Now I'm trying to track to see if some of the files or folders didn't get uploaded. Which files would have the Oauth2 code to check?
- Edited
cherrie Install the plugin (Admin Panel > Manage > Plugins), enable the plugin, and then you’ll see OAuth2 - Google as an Authentication option in the email's Remote Mailbox tab.
On the Plugins tab, there are no Plugins listed to enable (none listed). Instructions said to place the plugin into the include/plugins folder. Where do I find the plugin to place in the folder?
- Edited
cherrie did you miss the Add New Plugin button?
I went to this webpage: ticket/scp/plugins.php and clicked on Add New plugin which took me to this:
ticket/scp/plugins.php?a=add
On this page it says:
To add a plugin into the system, download and place the plugin into the include/plugins folder. Once in the plugin is in the plugins/ folder, it will be shown in the list below.
On our download page, select your version (v1.17.3). In the list of plugins, select Authentication :: OAuth2.
Put the .phar in the "include/plugins" folder. Set permissions so the web server can read it.
Then you should see the plugin in osTicket, follow Kevin's instructions, and follow the rest of the guide.
- Edited
I set up the API in google by following the instructions. The API looks enabled. However, I'm getting this error from google:
xxxxxx has not completed the Google verification process. The app is currently being tested, and can only be accessed by developer-approved testers. If you think you should have access, contact the developer.
If you are a developer of domain.org, see error details.
Error 403: access_denied
In the Remote Mailbox tab, I clicked on the "Configure Authentication" error text and it gave me the same error. What to do now?
I haven’t run into that before but the error states the app is in test mode. You can publish the app and the error should go away.
Cheers.
I think I was able to publish the app. On the remote mailbox tab, I clicked on config button and no error popped up. I noticed that the outgoing smtp is disable. When I tried to enable, it asks me for host name and port. tried both ssl://smtp.gmail.com with port 465 and tls://smtp.gmail.com with port 587 but got an error:
Could not open socket: stream_socket_client(): Unable to connect to tcp://smtp.gmail.com:587 (Network is unreachable)
Don’t append ssl:// nor tls:// as it will auto detect the encryption method to use based on the port. Just do smtp.gmail.com port 587. Authentication should be set to "Same as Remote Mailbox".
Cheers.
still getting same error. See
Can you try to telnet to that host and port from the command line on the server? It saying it can’t reach it. Could be a firewall, blocked port, etc.
Cheers.
Never telnet before.... On my computer, I used the server's ip address and port 465. It prompted me to a blank page so I assume that I was able to connect.
Also, I contactd my host provider, and they gave me a different hostname but gave me a different error:
XOAUTH2 authentication mechanism not supported
Blank page means fatal error and/or crash so that’s not good. Also, that error means your host doesn’t support OAuth2. They likely support old, basic authentication.
Cheers.