I sent an inquiry about when we can expect a new release at https://osticketawesome.com/contact/. If they provide an answer, I'll post it here.
Hi All,
I am as excited to see the newest version of OSTicket be adopted and transformed into what we know and love by the OSTicket Awesome team however I can imagine this process can take a bit of time. There is a bit of good news however, those of us that are still using the OSTicket Awesome (some previous version that doesn't have OAuth2 within it) have a bit of reprieve.
Although Microsoft is / has now disabled Basic Authenticaiton, administrators in Microsoft 365 tenants can perform a one-time re-enablement of the Basic Authentication protocols with the final deadline for them being shut off now being December 2022 (giving us all a couple months to wait for the OSTicket Awesome version that has the OAuth2 functionality within it). Please see the article linked below for more details:
I know this isn't a fix, more of a patch for now but I figured I would share it with anyone who might be interested.
Looking forward to the new version of OSTicket Awesome when it arrives!
Thanks and have a great day!
Well, if I had known that, sure, but now I was under the impression that we were forced to update, so we did that. I'm not about to downgrade now. It was very cumbersome getting oauth to work by the way...
If the awesome update doesn't come very soon I'll be forced to look for a different solution.
Thank you for posting that workaround, @Stephen@EhOS.
But rest assured everyone, I should be releasing the next version this week. I will update this thread when I do.
Good to hear that there will be an Awesome version in the next week. I have a plain test version working with OAuth. I could test there if provided an early release version.
Setup is no worse than other applications. I had a hell of a time with our ERP software as it did not give verbose error messages. The osTickect OAuth gave pretty good error messages. The biggest issue I had was that I had with osTicket was that I had to make my test instance available publically. I also had to update the cacert.pem.
I extended my opt-out, but I don't really trust MS to not re-disable legacy auth.
Thank you.