-
|
Hey there, hope you're doing well.
But no luck, after searching for a few posts and forums. Any idea, or suggestions about what could be causing that error? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
|
Hi @fmertins , have you looked at the following posts:
In a nutshell, either your SB org or your proxy service that sits between data loader and SB org presents a cert to data loader that is not verified by a Certificate Authority. The fix is to add that cert to the default keystore for your JRE on your deskthop. A workaround is to switch to browser-based OAuth login (it is supported in the batch mode too), which will make your process scripts interactive - they will prompt you for login through a browser window before proceeding. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, thank you, today we realized the cause of the error: we were using that "myorg.sandbox.lightning.force.com" URL pattern but instead, it has to be that "myorg.sandbox.my.salesforce.com" variation. That goes on the DL's properties file, for example directives like:
Interestingly, if we ping both URL patterns, they both seem to point to "dfw.edge2.salesforce.com"; not the very same IP, but very similar ones. They both work just fine in terms of opening them on the browser, but it looks like there's a difference when DL will use them. Does make any sense? (On the browser, "myorg.sandbox.my.salesforce.com" ends up being redirected to "myorg.sandbox.lightning.force.com") |
Beta Was this translation helpful? Give feedback.
-
|
Hi @fmertins , it is an interesting find indeed. I tried by setting So, even storing the cert into JRE's keystore would likely not have helped in your case. We will investigate this further and see why |
Beta Was this translation helpful? Give feedback.
-
|
PR #804 contains the fix to retry browser-based OAuth login by using |
Beta Was this translation helpful? Give feedback.
-
|
Hello, thank you again for the prompt support and attention here, all the best! |
Beta Was this translation helpful? Give feedback.
Hey, thank you, today we realized the cause of the error: we were using that "myorg.sandbox.lightning.force.com" URL pattern but instead, it has to be that "myorg.sandbox.my.salesforce.com" variation. That goes on the DL's properties file, for example directives like:
Interestingly, if we ping both URL patterns, they both seem to point to "dfw.edge2.salesforce.com"; not the very same IP, but very similar ones. They both work just fine in terms of opening them on the browser, but it looks like there's a difference when DL will use them. Does make any sense?
(On the browser, "myorg.sandbox.my.salesforce.com" ends up being redirected to "myorg.sandbo…