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.
OAuth2 Microsoft Not Working
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.
- Edited
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:
- mails from Inbox didn't fetch
- one of ticket had a time of 'last Update' about 02 AM
- token are valid IMAP and SMTP
So I made:
- go to AOuth2 MS Remote Mailbox, IdP config and click on 'Submit'
- and that same Remote Mailbox disable 'Email Fetching' and click 'Save Changes', next enable 'Email Fetching' and click 'Save Changes'
After that mails fetch from Inbox.
Conclusion,
- why mails won't fetch byt one of ticket was update
- witch my actions cause fetch emails from Inbox
Sounds like you need a cron job to automatically poll emails. Then each time it fetches it will update the tokens.
Cheers.
6 days later
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.
I've got all 3 of my installations updated and working fine following the guides however when the ticket is created for or by a Gmail user the replies are being blocked.
Our system has detected that this message is not
RFC 550-5.7.1 5322 compliant: duplicate headers. To reduce the amount of
spam sent 550-5.7.1 to Gmail, this message has been blocked. Please review
550 5.7.1 RFC 5322 specifications for more information.
Any ideas whats wrong?
Thank you
I've found the issue... Outgoing settings were disabled, the old port setting was 25. Changed to 587 and enabled. All is good.
[insert comical abuse here]
- Edited
Can someone please help me to setup Oauth2. I can't figure out what am I doing wrong.
This is my setup:
After I request the approval, it sends me back to osTicket log in page. Request is approved by admin, but nothing changes in osTicket.
I get this error and if I try to submit again it is still asking to request approval for the same things that are already approved.
Any ideas what should I check or if I am missing something?
Please follow the exact steps listed in the documentation here:
Also, you'll probably have better luck registering the app as Multi-Tenant.
Cheers.
I have this error when try to configure authentication
Double checked all settings, seems the token can't be redeemed, first part of getting authorization code works.
Can I have a detailed log to know what is the server response??
Thanks
It looks like you either didn’t use the correct endpoints or your connection is being refused. Double check your endpoints and make sure you are using the v2 Authorization/Token Endpoints. If all else fails contact Microsoft.
Cheers.
- Edited
KevinTheJedi
Thank you for answering back to me,
I was using these instructions https://github.com/osTicket/docs/blob/3b6b623c026c15bb267e404a4afd72b19d29f035/OAuth2/Microsoft%20Authorization%20Guide.rst but they look the same like the one you gave me.
Although it is possible I have missed something (I will double check) and I will also try with multitenant option, I have noticed that in one step I differ from the instructions:
"Now with all the information filled in you can click Submit and you should be redirected to Microsoft to authorize the connection.
Here it is very important to login to the email you are trying to configure in the helpdesk. Once logged in as the system email you are trying to configure, you can opt to Consent on behalf of your organization, and then click Accept."
Here when I click submit, I do not get this page and option to consent on behalf of my organization:
Instead I get only option to Request approval (I am logging in with the email I am trying to configure in the helpdesk):
Afterwards, when admin log-in with his account on his PC he only has this option:
He accepts the request but that doesn't work, when I log-in to the osTicket I get the same error again and it is asking me to Request the same approval again... and I am stuck in the loop.
"Unable to update this email. Correct any errors below and try again.
Configure Authentication"
What should I change to get the option to consent on behalf of my organization and accept, instead of the requesting approval option that I am getting?
Does this helpdesk account needs to have admin rights for the organization? or there is another step I have missed?
Thank you
Sounds like you didn’t grant admin consent in the app registration for the API Permissions.
Cheers.
Okay so just encountered this today and actually came across a fix! So all you need to do is follow the below guide:
So apparently, with stricter org setups, you have to grant admin consent twice, once on the API Permissions and again under Enterprise Applications > click app > click Permissions > grant admin consent.
Cheers.
KevinTheJedi Thank you Kevin,
Option 3 did the trick for me.
Unfortunately I cannot keep those settings due to our company policy.
Hopefully if will continue working now after initial approvals have been granted.
ranved82 Just to confirm, I did migrate our test server to 1.17 using OAuth yesterday and noticed this. It was all sorted after allowing users to grant consent to apps, and I did turn it back to admin approval required afterwards and everything is still working. It should be fine without having to change this setting again unless the app itself is replaced.
KevinTheJedi
Thank you for reply. I solved. I discovered the problem was related to PHP.ini that not have openssl extension enabled.
So Endpoint refused connections because were not requested with the correct transport protocol.
BR
5 days later
I also had the Auth Failed error and found that the default scopes in the Add on are not correct.
I added the following and everything is good to go.
https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/POP.AccessAsUser.All https://outlook.office.com/SMTP.Send