Skip to main content
Solved

After new SSL certificate FME Flow apps complains about Rest API

  • February 17, 2025
  • 2 replies
  • 45 views
worjak
Contributor
Forum|alt.badge.img+3

 I updated the pfx cetificate file according to this :

Configuring for HTTPS

Basically updating these lines i server.xml: 

keystoreFile="<file>"
keystorePass="<password>"

Now apps complains about REST API? Why? - what to do?

What is the realtion between the SSL certificate and the FME flow Rest API? Where to find information about this? 

Best answer by worjak

Ok, thanks. I found out. Since my friends in the IT-department changede the Certificate issuer from a commercial (Trusted CA) to a company issued certificate I need to do an extra step in the configuration procedure (Configuring for HTTPS). 

So step 6 is not optional for my setup but the task is quite easy - you just have to know!

 

I didn’t realise what the change meant till now. It has some benefits regarding cost and maintance.

 

View original
Did this help you find an answer to your question?

2 replies

j.botterill
Influencer
Forum|alt.badge.img+34
  • j.botterillInfluencer
  • Influencer
  • February 17, 2025

Hi Worjak, maybe start your troubleshooting using this guide

By securing the FME Flow REST API with an SSL certificate, you ensure that sensitive information, such as login credentials and data payloads, is protected during transmission. The REST API is responsible for all actions under the Flow UI.

  1. Are you using a FQDN url instead of the machine URL that comes by default when it was http?  Maybe your IT needs to make an entry in the domain. Or you need to update the server.xml WEB_URL
  2. Check you have correctly entered the path and file by navigating to the .keystore and double check your text in Server.xml.      keystoreFile="<FMEFlowDir>\Utilities\jre\bin\tomcat.keystore"
  3. You can access the tomcat and Catalina.logs on the FME host machine and find out what errors it might be complaining about. <FMEServerDir>\Utilities\tomcat\logs
worjak
Contributor
Forum|alt.badge.img+3
  • worjakContributor
  • Author
  • Contributor
  • Best Answer
  • February 17, 2025

Ok, thanks. I found out. Since my friends in the IT-department changede the Certificate issuer from a commercial (Trusted CA) to a company issued certificate I need to do an extra step in the configuration procedure (Configuring for HTTPS). 

So step 6 is not optional for my setup but the task is quite easy - you just have to know!

 

I didn’t realise what the change meant till now. It has some benefits regarding cost and maintance.

 

nielsgerrits
1 person upvoted this
  • nielsgerrits
    nielsgerrits

Reply


Most helpful members this week

Community Stats

30,851
Posts
116,969
Replies
38,683
Members
Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.