.NET Server Mini App fixes needed for new UPS Shipping OAuth change
We currently have an internal website built in .NET called Fluke Metteam our team uses to run calibrations on different types of equipment. Within that softwasre there is a shipping section that allows for our team members to create a RMA shipment for the desired customer in Metteam, but then would have to go to login to our UPS account and recreate the shipment there to actually produce the shipping label PDF. That is how the Metteam software worked natively until about 5 years ago. We contracted a freelancer on this platform to create a "mini app" that once our team member hit the Ship button in Metteam - it would then talk to our UPS account (via basic auth UPS API Client ID, Password, and UPS Acct. number), create the shipment from data inputted into the ship to fields of the Metteam software, and finally produce the UPS shipping label image where you could either print it or save PDF. Since that time, UPS has changed from Basic API authentication to the new OAuth requirements consisting of Client ID, Client Secret, temp tokens etc... and thus it broke our "mini-app" and the Shipping function is now broken. We need our existing mini-app's code to be updated utilizing the new OAuth parameters and tested to ensure everything is working as it once did. If you accept this work - you will have access to the web server along with our UPS API Developer account - and onsite IT to help with any questions. This is a quick job hoping to finish this within a day or two.