Using the latest 0.6 Oauth plugin, V1.17, clicking on "Config" of remote mailbox produces a blank window.
No PHP errors, IIS log just shows that a 500 was in fact thrown.
Any ideas? Not sure how to proceed on this one. We have several instances that are at risk to stop working once Microsoft's basic auth officially ceases functioning.
Do other popups and help tips work? If not then AJAX is not working properly and you need to figure that out. If it’s just this particular popup then you need to check all logs (general server logs, webserver error logs, PHP error logs, MySQL/MariaDB error logs, osTicket System Logs, Browser Console logs, etc.) for any related errors. 500 errors are very generic and hint at a deeper issue which should be logged somewhere. Check your PHP configurations to ensure you have logging enabled and have a log file set, for Apache do the same, and for MySQL do the same.
Cheers.
Hello, we are trying to upgrade to 1.17 (windows IIS and php 8.1.11). We get this error after authorizing with the mailbox user we want to IMAP fetch from. I removed our tenant identifier but not sure how to resolve this.
cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://login.microsoftonline.com/TenantIDRemoved/oauth2/v2.0/token
You’ll need to download the cacert.pen from curl, add it to your PHP install, and edit your PHP.ini file to set the full path to the file for the curl.cainfo directive. For more info please google the error or go to the link specified in the error.
Cheers.
ellisonrje In case anyone else runs into this issue it was the azure license type applied to this account. I had to have it changed from A1 to A5 and then it started working.
KevinTheJedi Thanks - that worked!
I'm having a similar issue, no matter how many times i send the app over for admin consent and approve it as an admin I will be asked to consent (even with the oauth plugin modification I followed in my previous post).
The one difference you can make however is you only need to give Application Administrator permissions to the account, not full global admin. This is enough to allow them to email account to admin consent the app themselves.
Look at my response here:
Cheers.
KevinTheJedi It seems that the old Oauth plugin (0.3) was holding on to the data for the email account somehow (probably in the database). We removed and recreated each email account in osTicket and finally, the window was populated correctly. We still aren't up and running yet, but we're down to "invalid_client". Now leaning towards some sort of misconfiguration in Azure / our osticket instance.
Hi,
I was very big problem to activate oauth2 with microsoft. But I have additional problem - I use shared mialboxes (before oauth2 I used this shared mialboxex, but now I cannot use it).
Do You have any solutions (via powershell) to add access for aplication using this shared mailboxes?
Not at this time no. You can customize the code but out of the box this is not possible. We do hope to add this support in the future.
Cheers.
osflake I'm using shared mailboxes too, and had no issues setting this up following the documentation. The key thing is you need to sign in as this shared mailbox directly, not as a delegate (it also helps to temporarily allow users to grant consent to apps, as it'll be the shared mailbox accounts doing this, not your administrator account).
Interesting, I must be thinking of aliases. I figured shared mailboxes don't have their own login but seems I was wrong in that assumption.
Cheers.
KevinTheJedi
You can log in to shared mailboxes using password but you have to set SMTP rules via powershell
Hi,
I use de configuration for OAuth2 in Outgoing SMTP and it works, but when i press "Save Changes" I get the error "Unable to connect via TLS" there is any idea that why I have recived this error?
regards
As it states it’s unable to connect via TLS. This can be due to many reasons so you’ll need to check your logs on your server for anything related. I would also check to ensure you have OpenSSL installed and updated on the server.
Cheers.
mbanyard, Thank you for the snippet. I migrated over from Apache on Ubuntu to Windows Server with IIS 10 and was pulling my hair out trying to get oAuth2 working, additionally, I had delete my original email profile and create a new one. Once I added the snipped to my web.config and created the new profile, the oAuth2 worked without error. Thank you all for the fantastic work you do and to the support community! My config is using Google Email in a Google for Workspace Environment for anyone that was curious.
Hi Huntmknox, did you ever get your NGINX configuration to work with Oauth2 authentication. I have the same issue you mentioned on 9/16/22 where I see the token in the address bar but the page shows up with "Not Found."
