I am currently on v1.11. Using POP & SSL to fetch mail Our engineering department is going to be moving all POP accounts to Modern Auth (OAuth) from Legacy Auth. Can this be configured in v1.11? I don't see the option. Upgrading - if we upgrade to the latest version, does it provide for Modern Auth? Any knowledge/help with this would be greatly appreciated!
Modern Auth needed instead of Legacy Auth for POP email
OAuth2.0 support has been in the works. Google’s new cutoff is May 30th so we are dedicating a lot of time to it now to meet the deadline.
With this being said v1.11 is very old and outdated and had many, many issues which is why it was dropped very quickly for the subsequent version. In any case it’s highly recommended to upgrade to the latest stable versions of v1.15.6 or v1.16.1 to get the latest security patches and to take advantage of the latest features and bug fixes.
Cheers.
Thank you! I will be upgrading to 1.15.6 soon. I would need to upgrade PHP to go to 1.16 and I don't want to throw it all together and have to figure out what I'm troubleshooting if there are issues. I did not know that Google had a cutoff date of May 30th. That is good news for me because our Engineers are targeting the October 1st date. My manager sent me a link on how to set up email piping. I don't know if this would fix the OAuth need or not. Perhaps my best option is to upgrade to 1.15.6 and then wait to see if a new version comes out that supports OAuth. Your thoughts?
Yea email piping would get around that as you don’t have to authenticate on osTicket side, you just pipe the mail (locally or externally).
Here is the message shown when you go to LessSecureApps docs:
Cheers.
Again, thank you. I am going to get to version 1.15 and then wait until May to see if a version is released that supports OAuth. I have until October when Microsoft ends it. Piping is plan B.