Skip to main content

Hi,

 

We have used same wild card certificate certificate from GoDaddy and used in both IFS Cloud and PSO.

They are accessible only within the corporate network.

 

When setting up the integration from “IFS Optimization Framework Configuration Assistant” it throws below error.

 

Validating IFS Cloud callback URL failed. Error message was: PlsqlapServer.ERRINV: ExecutionException from Sender thread
Caused by: ifs.fnd.connect.senders.ConnectSender$TemporaryFailureException: Exception while sending data
Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderExceptio. If this is an external URL which can be accessed only from IFS Optimization server, it cannot be validated using the configuration assistant. The URL may still work when accessed externally. Do you want to continue?

 

 

Have you came across this issue before?

 

Thanks in advance.

Hi!

Please check following KBA:

https://support.ifs.com/csm?id=kb_article_view&sysparm_article=KB0047334


Best regards
Roman

Thank you Roman. Let me try.

Hi @roklde ,

Thank you.

The first error is sorted by importing the certificate to ifsapp-odata and ifsapp-connect pods. Now I’m getting below error. You mentioned to check on “IFS Cloud Callback URL Thumbprint”. But I think that is for self signed certificates. But we are not using self signed certificate.

 

 

Failed to connect to IFS Optimization server account Default. Error message was: com.ifsworld.fnd.odp.api.exception.ProjectionException: javax.ws.rs.ProcessingException: java.net.UnknownHostException: UnknownHostException invoking https://pso.XXXXX.com/IFSSchedulingRESTfulGateway/api/v1/scheduling/session: pso.platnedcloud.com. The user IFSSCHEDULING and the parameters OpenIdAuthority, OpenIdClientId, UserNameClaim may need to be set up manually. Do you want to continue?

 

Could you please just try it anyways? Also make sure that the PSO User/Password is correct and check PSO Events for any errors. PSO is also configured properly for HTTPS, right?

Best regards
Roman

Thank you for your assistance @roklde,

I did the configurations but still getting the same error. Yes PSO can be accessible through HTTPS successfully.

 

Best Regards

-San

Are you sure that IFS Cloud can reach PSO? Could you please check this from inside the Kubernetes Cluster? Also is the certificate properly installed on the PSO Server - do you see any certificate warnings when browsing to the PSO URL? Lastly, is PSO installed into a Kubernetes Cluster as well? If yes, the RESTful Gateway is located at https://<host>/gateway

Best regards
Roman

Thank you @roklde,

I can see IFS Cloud reach PSO successfully. And PSO is installed on a different windows servers. It is not a Kubernetes Cluster.

 

Ok. Did you check the PSO Events? Are you seeing 401 unauthorized messages when you try to make the configuration?

Best regards
Roman

Hi @roklde 

No, I don’t see any hits in event logs when I’m trying to connect to finish the configuration.

 

Thanks and Best Regards

-San

Thank you @roklde,

I can see IFS Cloud reach PSO successfully. And PSO is installed on a different windows servers. It is not a Kubernetes Cluster.

 

Hi San, can you also try it with  https://pso.XXXXX.com/IFSSchedulingRESTfulGateway/? If you don’t see anything inside the PSO Events the message isn’t even reaching the PSO Server. In addition, you might also check IIS Logs.

For the certificate thumbprint config, please also make sure it’s correctly configured as described in the PSO Administration Guide:
 


Best regards
Roman

Reply


Terms & ConditionsCookie settings