OAuth 2.0 support? (D7)

Yes, UPS just sent this out:

UPS has implemented an OAuth 2.0 security model for all APIs to enhance the overall security for our customers to reduce fraud and provide enhanced API capabilities. This change impacts your current API integration and requires you to make updates to your existing application interface.

How will this impact my API integration?

• Beginning June 5, 2023, UPS will no longer issue API access keys

• On June 3, 2024, access keys will no longer be supported for authentication to UPS APIs

• You will need to obtain OAuth API credentials from the new UPS Developer Portal and update your security protocols to OAuth 2.0 prior to June 3, 2024 to continue transacting with UPS APIs

• Any legacy UPS API integrations using XML, SOAP, or legacy JSON payloads will also be required to convert to the RESTful APIs

We have created an API access key migration guide to assist with your migration from access keys to OAuth 2.0. If you obtained an access key to provide to a 3rd party please notify them of these changes immediately.

I received that Oauth email as well. Is this and update that is being worked into the plans for this module? Any early idea of a release date for such an update?

The bigger concern seems to be that switching to OAuth requires switching to their new REST API - currently, we're using a library that uses the XML API.

Is there an ETA on the OAuth2 support?
I just implemented a Emcommerace site on Drupal so I do not have the older APIs

I am implementing Drupal Comm on a few of my sites. Is there an updated ETA on this.. is there any shipping module that can can effectively co-exist with Drupal Comm?

Making this a critical feature request as UPS is actively phasing out the old authentication system as of June 2023, and there will be seven months between when the old API is completely disabled (June 2024) and Drupal 7 is no longer supported (January 2025).

As for when this will be done, I suspect some of the companies using it will have to fund the development rather than waiting for the current maintainers to do it.

FYI #4 suggests this would need to be a major rewrite of the module, presumably creating a 7.x-3.x release.

Re: #7 - How much funding may be required and how shall it be raised? We are using this module and would like to see it updated.

What can we do to help get this issue resolved? We will soon be short on time.

Here's a link to the related issue for the gabrielbull/ups-api package
https://github.com/gabrielbull/php-ups-api/issues/370

So far the conversation seems to be about alternate options.

We are still interested in supporting this module being updated. EOL for D7 has been pushed several times now and it's reasonable to expect there could be more than seven months for continued use of this module.

I recommend getting in direct contact with Centarro → or other dev studios and enquire about going in on paying for the work to be done.

Thank you. I have written them and will post again after I receive a reply.

I have received three replies from rszrama for Centarro, with a nearly two week wait after I followed up additionally for each one excepting the first. Without having heard a precise figure yet, I can at least relate that updating the module would require compensating them for potentially weeks of work.

I met with HeroDevs a few days ago to learn more about their Never Ending Support for Drupal 7 since it is to be EOL in January, 2024. I was told there has been interest expressed to them by multiple prospective clients about support for this module among the other modules they plan to support, but I haven't received an answer yet as to how/whether a rewrite of this module before then would be facilitated.

What are the possibilities for this version of the module to move forward? I see the D8+ version has code to review for OAuth compatibility. Can some of that cross over?

HeroDevs wrote that they will not be updating the Commerce UPS module to use the OAuth protocol in their never ending support.