KevinTheJedi I made the changes, but still in "invalid client".. I download and reinstall the plugin with the same result
edit:
I made a fresh install, without de data of the old OST, and work... so something about the original OST is broken...
Did you enable and consent to the needed scopes in your Azure App? Please go back to my linked guide and follow all the steps.
Cheers.
lupo_gris
These settings have worked for me
email Address Attribute part, you have different, based on your AD settings
Client Id: *
IdP Client / Application Identifier
Client Secret:
IdP Client Secret
Scopes: *
Comma or Space separated scopes depending on IdP requirements
offline_access https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/POP.AccessAsUser.All https://outlook.office.com/SMTP.Send
Authorization Endpoint: *
Authorization URL
https://login.microsoftonline.com/common/oauth2/v2.0/authorize
Token Endpoint: *
Access Token URL
https://login.microsoftonline.com/common/oauth2/v2.0/token
Resource Details Endpoint: *
User Details URL
https://outlook.office.com/api/v2.0/me
Email Address Attribute: *
Please consult your provider docs for the correct attribute to use
emailAddress
Callback Endpoint: *
Redirect Uri
https://YourSupportTicketAddress.com/api/auth/oauth2
Our token expired and app won't fetch emails. So, app should have extra permissions in Azure App? Anyway, on SMTP configuration token is valid.
Update: After go to setting token and click on confirm, token refresh and valid but still main won't fetch emails form Inbox.
I tried with plugin version 0.3 and the redirect url does not work. it just redirects to the homepage when authenticating.
Version 0.5 does not open configuration, just a blank popup.
Any here with a working version?
sander4000
Check the network traffic with the developer tools (usually "F12"). Sometimes it shows you the error as soon as you got redirected.
KevinTheJedi yes, all configuration are correct... in a fresh ost (without data) works perfectly... I made a pre version upgrade (1.14 - 1.16) and from 1.16 to 1.17 and the OST with data works.. thanks a lot for the help
Is the scope of what is being worked on just generating the token? Is fetching and sending mail also implemented?
Of course. We completely changed the package for mail from PEAR to Laminas-Mail which supports Modern Auth.
Cheers.
I must be missing something. I'm on 1.17rc4 and this is what I'm seeing:
fyi for this issue, our organization was doing something weird with our firewall and SSL certs. After going around that everything worked. thanks
You have cURL issues on your server. Please follow the link displayed in the error to review the possible resolutions. this is outside the scope of osTicket software.
Cheers.
I have no idea why; I am unable to replicate this..
Are you using a test application? Are you sure you set the token expiration to a long period of time?
Cheers.
update: so the curl error was because of having "organizations" in the urls, changed them to "common" and now it appears to do nothing when saving the config, it just dumps me back to the login screen of the ticket system.
Then that most likely needs you don’t have URL Rewriting enabled on your web server. Or maybe wrong endpoints. You need to go to app reg, click the app, click Overview, and click endpoints. You need to use the first two URLs (Authorization v2 and Token v2).
Cheers.
Hi,
We have a test app on 17 RC4
I didn't change token expiration yet, but today morning I noticed:
So I made:
After that mails fetch from Inbox.
Conclusion,
Sounds like you need a cron job to automatically poll emails. Then each time it fetches it will update the tokens.
Cheers.
Thanks for your suggestions!
The last bit of my puzzle was about fetching messages, which simply needed to be scheduled by a Cron job.
Running "RC4"
I made a cron job, before a problems with fetch. Anyway problems gone 
but I still I don't know what cause resolve problem.
