Skip to main content
Solved

Certificate to for HTTPS URL of FME Server

  • September 21, 2020
  • 4 replies
  • 209 views

akheirabadi
Contributor
Forum|alt.badge.img+5

Hi all,

 

I have an issue in getting the certificate to work for HTTPS URL of FME Server.

 

I have used this URL as reference: https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/configuring_for_https.htm

 

I did use these steps to create Keystore:

• Open a command prompt as administrator and navigate to the Java bin directory (C:\\Program Files\\FMEServer\\Utilities\\jre\\bin )

• Run the following command to create a new keystore file:

keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore

• After running the previous command, you are prompted to set a password for the new keystore and specify the server domain name (for example, myserver.mydomain (My FME Server) as your first and last name.

• Password: mypass

• When prompted for the password for the alias <tomcat>, press RETURN.

• A new keystore is created in C:\\Program Files\\FMEServer\\Utilities\\jre\\bin\\

• Copy the new keystore file to the tomcat directory in the FME Server installation: C:\\Program Files\\FMEServer\\Utilities\\tomcat\\

 

 

For Certificate I did tried to use different ways.

Way1: CA-issued certificate:

1. Generate a certificate signing request (CSR):

keytool -certreq -keyalg RSA -alias tomcat –file certreq.csr -keystore tomcat.keystore

2. Submit the CSR (certreq.scr) to your CA to obtain a certificate, issued a certificate (export from CA)

3. Import the certificate into the keystore. Depending on the web application server, you may also need to import a root certificate (consult your web application or CA's instructions).

keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file TomcatCer.cer

 

Way2: I’ve also tried this way after unsuccessful process, because I was thinking the problem is with certificate, so I remove Keystore, recreate it and I’ve done following steps. (After I’ve done the whole process and it was unsuccessful, I did this)

1. Export valid certificate which I had on that server

2. Import the certificate into the keystore. Depending on the web application server, you may also need to import a root certificate (consult your web application or CA's instructions).

keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file GoDady.cer

 

Configure Tomcat

I’ve also done the configuration based on document on these three XMLs and I think its ok, because except certificate issue, I don’t have any issue.

• Configure server.xml

• Configure web.xml

• Configure context.xml

 

And finally I’ve modified Service URLs to Use HTTPS on FME Server.

 

But I’m getting this error and I couldn’t find a way around this ( I did try two ways of configuring certificate as I explained)

I clicked on invalid certificate and I can see all the setting I’ve done when I was creating keystore.

 

So it looks like its not having valid certificate.

 

Just wondering what am I missing and what should I do to fix the issue? Thanks.

Best answer by akheirabadi

Thanks guys, the problem was related to certificate. It has been resolved by using the right certificate.

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

4 replies

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • September 21, 2020

Hi @akheirabadi​,

 

Out of curiosity, have you tried running through the FME Server Troubleshooting HTTPS and SSL article? This article covers a number of things to check when running into issues with configuring HTTPS on FME Server.

 

Please let me know if that doesn't resolve the issue!


akheirabadi
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • September 21, 2020

Thanks @chrisatsafe​  for your response.

 

Yes I did check that one before and my problem is number 7 in the list, but I cannot find where I did mistake. I tried all steps as I explained on two servers and got the same problem.

 

Cheers


hkingsbury
Celebrity
Forum|alt.badge.img+51
  • Celebrity
  • September 22, 2020

akheirabadi
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • Best Answer
  • September 28, 2020

Thanks guys, the problem was related to certificate. It has been resolved by using the right certificate.


Reply


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