Support for new UPS API security requirements

[TraceyC77]

I recently received an email from UPS sent to my developer account outlining changes to the security model for their API access. Do you plan on supporting this change?

The main points are • 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

Full documentation: Upgrades to the UPS API Security Model

Migration Guide

[pullingshots]

Yes, I plan on upgrading to the RESTful API later this year. And pull request are always welcome :)

[TraceyC77]

Thanks for confirming, good to know. If you would coordinate the work, I would be willing to help with coding and testing. My organization has a UPS integration I help maintain.

[pullingshots]

That's great. I'll reach out when I have an upgrade plan in place.

[icyavocado]

Still need to work on sub xav and sub track

[icyavocado]

I just submited another update to include track into the API. I wasnt able to get the same data to pull, the ship_date or PickupDate is not part of the JSON response anymore. Please let me know if that is false, and I can fix the code.

[icyavocado]

Added xav sub, will need Address Validation API enabled for request to return response.

[icyavocado]

I will work on adding my tests to the repo tests for completeness.

[icyavocado]

I fixed the test ups.t so it uses the new credentials. And also fixed a few minor issues with exporting, importing, indentation, and checking for undef.