It is relatively safe to assume that the devs will talk about it and make their own determination as to if this should be a planned feature.

3 months later

Just got this email from Google. Looks like Gsuite is moving to require OAuth authentication for checking/sending email inboxes using the IMAP protocol.

Starting February 15, 2021, G Suite accounts will only allow access to apps using OAuth. Password-based access will no longer be supported.
Dear Administrator,

We’re constantly working to improve the security of your organization’s Google accounts. As part of this effort, and in consideration of the current threat landscape, we’ll be turning off access to less secure apps (LSA) — non-Google apps that can access your Google account with only a username and password, without requiring any additional verification steps. Access through only a username and password makes your account more vulnerable to hijacking attempts. Moving forward, only apps that support a more modern and secure access method called OAuth will be able to access your G Suite account.

Access to LSAs will be turned off in two stages:

June 15, 2020 - Users who try to connect to an LSA for the first time will no longer be able to do so. This includes third-party apps that allow password-only access to Google calendars, contacts, and email via protocols such as CalDAV, CardDAV and IMAP. Users who have connected to LSAs prior to this date will be able to continue using them until usage of all LSAs is turned off.
February 15, 2021 - Access to LSAs will be turned off for all G Suite accounts.
What do I need to do?
To continue using a specific app with your G Suite accounts, users in your organization must switch to a more secure type of access called OAuth. This connection method allows apps to access accounts with a digital key instead of requiring a user to reveal their username and password. We recommend that you share the user instructions (included below) with individuals in your organization to help them make the necessary changes. Alternatively, if your organization is using custom tools, you can ask the developer of the tool to update it to use OAuth.

Came here to comment about this same email from Google. We have a little bit of time, but I want to know how to fix this down the line.

12 days later

FOLLOWING:

whilst i don't need this for my personal helpdesk i do need it for a couple of NFP helpdesks i host

would even be happy to contribute a donation to get this across the line

h

@zeHamish

No need for donations as supporting OAuth is something on our list of Feature Requests and something we are looking to accomplish before the cutoff dates (as we use Gmail internally and this will affect us as well).

Cheers.

5 months later

Good day, do you have any news on this ?
I know Microsoft has push back, but it still on the horizon ;-)

Any think we can do to help ? Provide test environnement or test a upcomming merge request maybe ?

Thanks you again for all the work !

Hi, As Tomlaf, I'm interested in knowing if there are any news on this.

Best regards,
Rosa

a month later

I just want to throw my request for this as well. Just to add on and hopefully move it up the list. We are currently unable to fetch emails due to this issue.

3 months later

I just had to fight to get basic authentication turned back on for our osticket helpdesk using outlook365 with our local authority they managed it by putting an exception in but once MS turn it off those exceptions are ignored.

I was told they've extended it by 6 months because of Covid.

Either way its going to be a be turned off and schools can't use unapproved email providers

So we will be stuck with a dead helpdesk

Is there an update on the progress OSTIcket is making toward being prepared for the transition? It is coming!

ntozier Does this also apply to Google's transition? The article you cited only applies to Microsoft.

    Yes. It is essentially the same thing, both are disabling legacy authentication and only allowing oauth2.

      ntozier I know they are doing the same thing (disabling legacy auth), but did they also extend the deadline?

          nesretep Ì was told in October that nowadays there's no deadline for Google Gmail. When they finally stablish a deadline I supose that there we'll be some months more till they disable legacy auth.

            2 months later

            Any update on the Topic of OAtuth 2 to allow email fetching from Gmail, As the deadline on 15th Feb 2021 is nearing

            @Alamiah

            We are still working on implementing OAuth2.0 support. As for the deadline in February, Google posted this update:

            As a result, we are suspending the LSA turn-off until further notice. All previously announced timeframes no longer apply. Please be reassured that when we restart the turn-off timelines, you will still have a 12 month window from that start date to review and complete your migration.

            Cheers.

              KevinTheJedi Thanks for the update 😃
              Even i had a chat with Google Support personnel yesterday
              As per Google Support regarding the shutting down of Less Secure Apps
              "Less Secure Apps, I'd say that this is not going to happen as of now even though you may have received an email stating otherwise"
              "The reason behind basically is because of Covid-19 that it was extended"
              Note:- It can be implemented at any time, I request osTicket Developers to be prepared and does not let the ship sink, keep it floating by developing oAuth2 for osTicket

                Looks like your request is granted:

                KevinTheJedi We are still working on implementing OAuth2.0 support.

                  2 months later

                  Is there any update on this planned change to allow oAuth? I just received notice from our organization that they are going to disable Basic Authentication at the end of May, 2021. Even if Microsoft and Google extend their deadlines, I'm sure there are other organizations, like mine, that are trying to stay of the stated deadlines.

                  Microsoft has announced plans to disable Basic Authentication for Exchange Online for all tenants in 2021. To prepare for this change, [omitted] will require modern authentication for ALL applications, including those previously granted exceptions, by May 31, 2021.

                  Your application must use modern authentication to connect to Exchange Online by June 1, 2021, or it will no longer work.