Hi @hardik Thank you for your feedbackUnfortunately adjusting “ifscore.networkpolicy” Key didn’t have any effect. The Problem was, that the Routing Addresses had the %FILE_OUT% präfix attached.Our IFS Cloud DB is a copy from IFSAPP10, where this was the correct from. In IFS Cloud it seems %FILE_OUT% has no use anymore.After removing %FILE_OUT% we had the following application error message when using our DFS share in the file sender:ExecutionException from Sender thread Caused by: ifs.fnd.connect.senders.ConnectSender$TemporaryFailureException: Error while sending data to file Caused by: jcifs.smb.SmbException: Failed to connect to server Caused by: java.net.UnknownHostException: <servername>It seems that the ifsconnect POD isnt able to resolve the DFS / <servername> properly, even though the Middle Tier Host can.After replacing the DFS share with the FQDN of the server, the file transfer worked.
We had the same issue while setting up MT for IFS Cloud. The solution for us was to recreate the pfx by telling keytool to use specific PBE algorithms for encrypting both the private key and the certificate itself in the keystore with: -certpbe PBE-SHA1-3DES -keypbe PBE-SHA1-3DES -macalg sha1 Final creation statement:openssl pkcs12 -export -out final.pfx -inkey private.key -in certificate.cer -passout pass:<yourcertppw> -certpbe PBE-SHA1-3DES -keypbe PBE-SHA1-3DES -macalg sha1
FYI: Answer is yes, MWS cipher suite supports ECC.
Hi Charith,I can’t check the KBA, but the issue has been resolved. The trust anchor is not the windows certmgr, but the cacerts, which will get updated, when the certificate is being imported through a mws reconfigure.The resolution was to have the certificate chain manually created in this form: -----BEGIN CERTIFICATE-----SERVER Certificate-----END CERTIFICATE----------BEGIN CERTIFICATE-----INTERMEDIATE Certificate-----END CERTIFICATE----------BEGIN CERTIFICATE-----ROOT Certificate-----END CERTIFICATE---- After that the private key was added and then converted from CER to PFX.
Hi Sajith,In MMC → local machine:Root is in “Trusted Root Certifciation Authorities”. ICA in “Intermediate Certifciation Authorities” (info, the most current ica was missing there for some reason). Last we week the http node was running though. Server/Wildcard in “Personal”Certificates have been re-imported to local machine as local admin & mws rebooted, but so far we’re having the same result.But from IFS perspective the Trust Anchor = windows certificate storage?Thats already an important info, thank you.
Hi Joe,Hi mwilson Thank you for the feedback. We had the https://server:/client/runtime/Ifs.Fnd.Explorer.application method in use for sometime, but from time to time we had to recreate the C:\Users\xxx\AppData\Local\Apps\2.0 cache on clients devices. But we’ll be taking another look at this approach again.BR,Cesar
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
