UPS OAuth Authentication Issue

-- url of the page with the problem -- : grandprix-software-central.com/index.php/shopping
-- HikaShop version -- : 6.1.0
-- Joomla version -- : 5.3.3
-- PHP version -- : 8.2.29
-- Browser(s) name and version -- : Firefox 142.0.1
-- Error-message(debug-mod must be tuned on) -- : An error occurred. The connection to the UPS server could not be established.
250002 Invalid Authentication Information.

I am trying to add UPS shipping with the newer plugin, as the old plugin no longer works. I've created a new account with UPS and added an app. I have Client ID, Client Secret, UPS account number, name, and address entered into the plugin.

I tried doing a web search on the error and came up with this webpage, which was a bit helpful:

https://octolize.com/docs/article/ups-labels-how-to-get-api-connection/#client-credentials

I added the ‘Authorization (OAuth)’ ‘Rating’, ‘Address Validation’, ‘Locator’, and 'Shipping' api's but am still getting the authentication error. I try my credentials in their demo plugin and they are accepted.

nicolas wrote: Hi,

The plugin has been out for a while now and many users are already using it. So I don't think the problem is in the plugin.
Indeed, the APIs not being added to your app would be a problem. Besides this, make sure you don't have any extra spaces in the input fields of the credentials.

No extra spaces are present. That's the first thing that I checked, along with checking that Client ID, Client Secret and Account# were correct. I managed to get rates showing up today. Not sure what that issue was, but that part is working now.

One issue that I do see is that the "Sort shipping service" set to "Cheapest" has no affect on the order that the rates are listed. It lists from most expensive down to cheapest no matter which option is selected.

nicolas wrote: Hi,

The sorting not working is probably just a caching issue because it works on my end.
HikaShop has a mechanism which automatically caches the rates returned by plugins for a cart and address combination to avoid too much querying of the shipping carrier servers. This way, the display of the pages is faster and there is less risk of hitting the querying limits of the APIs.
The caching is done with the user session.
So, logging out and then logging in again should clear the user session and thus make sure it is not a caching artifact.
Could you check on this ?

Even logging in from a different computer has the rates in largest to smallest order.

Thanks. Sorting is now working properly.