FedEx Plugin Configuration

Let me first apologize. i am new to working in nop commerce.
On the FedEx Plugin for nop commerce I have given it all the required information from our account but still it is giving me a Authentication failed any idea why?

I have it set to the URL: https://ws.fedex.com:443/web-services (What FedEx Documentation said to set it to.) with our customer production information in there too.

On the Logs I only get the short message of (Shipping (FedEx). Authentication Failed)

Is there a better way to test this information?

Make sure you have correct production access keys set up.
Try this url  https://gateway.fedex.com:443/web-services.

Also, make sure port number 443 is open (outbound, to call FedEx web service)

I am currently working with my network team to verify with 100% accuracy that port 443 is open for sending traffic on our server.

Is there any other way I can get more log information or any better way of testing our credentials in a know working environment just to help pin down my exact issue?

You can email me at [email protected] for a more secure transfer of information.

Thanks- Matthew

[email protected] wrote:

you can recreate the API calls in https://www.postman.com/ outside of Nop to confirm your credentials and view the responses from FedEx

af1racing wrote:

Thanks for that advice. I am having trouble finding an example post for FedEx through do you or any one else have an example request I could test with?

Thanks

see:
https://stackoverflow.com/a/60437984

Make a raw POST request with XML in Postman, replacing your Key, Password, AccountNumber, and MeterNumber credentials:



other request examples here:
http://www.fedex.com/us/solutions/wis/pdf/API_Direct_XML_Transaction_Guide.pdf

you can then change the URL and credentials for production values when ready, but check their best practices for any stipulations regarding hitting production before clicking send:
https://www.fedex.com/us/developer/downloads/pdf/FedEx_Web_Services_Best_Practices_Guide_V.1.1.pdf

I am still getting an authentication error via postman from my local machine I have gotten new keys from FedEx and copied and pasted them exactly still no change though?

I also tried setting up a new store and am running it on localhost. then configured the localhost plugin with the same keys I have on the server and it works over on the localhost site but still won't work on the server? Could it be product dimensions or something throwing an authentication error for FedEx because I am using the test products on localhost.

is their specific port settings that anyone is aware of to look at directly? From everything we looked at 443 is enabled and working properly but we are still getting the error.

Thanks- Matthew

looking at the code it doesn't really care if the request isn't authenticated, it only reports back any/all errors including an authentication failure, so I don't think it has anything to do with products

it does sound like it's purely an authentication issue, are you 100% sure you are posting test keys to  https://wsbeta.fedex.com:443/web-services/ and production keys to https://ws.fedex.com:443/webservices/?   they have 2 separate application processes for test vs production keys

there is a setting for the URL in the plugin configuration too

[email protected] wrote:
Then it would seem to be a networking or IIS problem.

So I am posting this more so I can look back on this issue and know what I did to fix my issue.

For FedEx when you go through the process of getting the test keys your account holder is sent an email with the password. You Do Not use the login password for this... Because I am developing a site for our account holder I was never sent the email with the correct password information.  When getting the production keys you can enter a separate email from the main account holder

Also how ever I had it configured in LocalHost Seemed to work but in reality it lied... Not sure how because fedex was the only shipping option selected and it still provided a rate for me but I know now that was not a true rate.