Skip to main content
Solved

IFS Connect integration with keystores

  • September 9, 2021
  • 3 replies
  • 399 views

Technical Toby
Superhero (Employee)
Forum|alt.badge.img+14

Dear Community!

For a customer, we are currently trying to add a connection between IFS 10 in the cloud and a server on customer side to connect securly.

 

This is for IFS Connect and a routing address to connect to a scale unit.

We have already added all possible certificates to IFS in the keystore window, but it still not working.
 

We are getting the error
Expetion while sending data
Caused by: ifs.fnd.base.SystemException: Exception while obtaining SSL socket factory
Caused by: java.io.IOException: toDerInputStream rejects tag type 45.

 

Any suggestions on that? 
Any help is appreciated.

We are now struggling with this topic for over a month now with nobody in IFS Germany being able to check on this.

Kind regards,

Tobias

Best answer by Technical Toby

The keystore window is only to be used for signing Documents.

 

It is not needed for the setup of secure integration with other systems.

 

We have removed the info from the Routing Address and the DNS Entry to the server is working now from the Cloud hosted Middleware Server.

 

We still have an issue, but that is related to coding.

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

Ragaventhan Sathananda
Superhero (Partner)
Forum|alt.badge.img+15

Hi @Technical Toby,

Could you please let us know whether the connection to Application hosted server to the server which is in customer side has no issues. First check that connectivity is there then you could see if the database wallet also has been updated with the same certificate sets. Just adding the certificates to Middleware server keystore might not help if the calls is directly going to the database. 


Technical Toby
Superhero (Employee)
Forum|alt.badge.img+14

Dear @Ragaventhan Sathananda 

AS this customer is in the managed cloud, I am not sure.

I do not have access to the VM there.

 

But the DNS Entry had been created via ticket CS0043426.

The call of the interface is via REST and not a direct database call.
 


Technical Toby
Superhero (Employee)
Forum|alt.badge.img+14
  • Author
  • Superhero (Employee)
  • 149 replies
  • Answer
  • September 23, 2021

The keystore window is only to be used for signing Documents.

 

It is not needed for the setup of secure integration with other systems.

 

We have removed the info from the Routing Address and the DNS Entry to the server is working now from the Cloud hosted Middleware Server.

 

We still have an issue, but that is related to coding.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings