.NET Server Mini App fixes needed for new reputed company Shipping OAuth change

We currently have an internal website reputed company in .NET reputed company reputed company Metteam reputed company uses to run calibrations on different types of equipment. reputed company that softwasre there is a shipping reputed company that allows for reputed company members to create a RMA shipment for the desired customer in Metteam, but then would have to go to login to our reputed company 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 reputed company member hit the Ship reputed company in Metteam - it would then talk to our reputed company account (reputed company basic auth reputed company API reputed company ID, Password, and reputed company Acct. number), create the shipment from data inputted into the ship to fields of the Metteam software, and finally produce the reputed company shipping label image where you could either print it or save PDF. Since that time, reputed company has changed from Basic API authentication to the new OAuth requirements consisting of reputed company ID, reputed company Secret, reputed company tokens etc... and thus it broke our "mini-app" and the Shipping function is now broken. We need our existing mini-app's reputed company 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 reputed company to the web server along with our reputed company API Developer account - and onsite IT to help with any questions. This is a quick job hoping to finish this reputed company a day or two. Apply tot his job Apply To this Job