Gone to replace the ssl certificate on the middleware server and I beleive to do this I run the ifsinstaller again but with the new certificate in the config file. When I go to run the installer it tells me it can't run as my kuberteties have now been depriciated and I should update by following the instructions. I can't find the instructions and I am worried my bin files are out of sync from the installed version. I have had a look at the build place but it only tells me the current version 23R1 but my install is still on 22R2. I have a backup of all the bin files but I don't know which ones relate to which version. Is there a list of which bins relate to which version?
Product Version: 22.2.4
Solved
IFS Cloud SSL Cert update
Best answer by Ragaventhan Sathananda
Hi
You may find your current kubectl version and HELM version from the main_config.json file inside your config folder. If it has outdated versions according to the error you get, then you need to go to your build place and download the latest bootstrap files and bootstrap binary files and merge the zip as you did during the initial installation and make that as the main configuration location (rename the old ifsroot folder as ifsroot_old and make the new one as ifsroot) and move/copy the yaml files to it and run the SSL certificate update again.
Hope this helps!
+15Hi
Please check if the below post helps your SSL wild card update.
If not please share a screenshot of the error you get as the issue is not clear to me.
Ragaventhan S - https://www.linkedin.com/in/ragaventhan-sathananda/
1 person likes this
Indeed I think I have the process but when I try and run the installer now I get this:
I think I have a mismatch of the bin files and my actuall install but I don’t know which version of the bin files I should use for 22.2.4.
Thanks,
Alex
+15Hi
You may find your current kubectl version and HELM version from the main_config.json file inside your config folder. If it has outdated versions according to the error you get, then you need to go to your build place and download the latest bootstrap files and bootstrap binary files and merge the zip as you did during the initial installation and make that as the main configuration location (rename the old ifsroot folder as ifsroot_old and make the new one as ifsroot) and move/copy the yaml files to it and run the SSL certificate update again.
Hope this helps!
Yes thats exactly what I need as my list has now updated to 23.1 so I can only see those. Could you send me a screenshot of the remote bins below also?
Many thanks,
Alex
+15
Here you go
Ragaventhan S - https://www.linkedin.com/in/ragaventhan-sathananda/
Hi,
I’m trying to update SSL certificate for IFS CLOUD 24.1 and the application is always signt by old certificate. I tried relative path, full path, set file as script parameter in cli and nothing worked. I deleted kubernetes cluster and installed it again, but now application is signed by autogenerated kubernetes self signed certificate, and not that pointed in configuration. Somebody had such a problem?
+14CgiTomasG wrote:
Hi,
I’m trying to update SSL certificate for IFS CLOUD 24.1 and the application is always signt by old certificate. I tried relative path, full path, set file as script parameter in cli and nothing worked. I deleted kubernetes cluster and installed it again, but now application is signed by autogenerated kubernetes self signed certificate, and not that pointed in configuration. Somebody had such a problem?
Hi, what was the solution?
Darshana Herath wrote:
CgiTomasG wrote:
Hi,
I’m trying to update SSL certificate for IFS CLOUD 24.1 and the application is always signt by old certificate. I tried relative path, full path, set file as script parameter in cli and nothing worked. I deleted kubernetes cluster and installed it again, but now application is signed by autogenerated kubernetes self signed certificate, and not that pointed in configuration. Somebody had such a problem?
Hi, what was the solution?
Hi, I think that it is the installation binaries files problem (23.2.6). I will try today with newest (24.1.2)
+14CgiTomasG wrote:
Darshana Herath wrote:
CgiTomasG wrote:
Hi,
I’m trying to update SSL certificate for IFS CLOUD 24.1 and the application is always signt by old certificate. I tried relative path, full path, set file as script parameter in cli and nothing worked. I deleted kubernetes cluster and installed it again, but now application is signed by autogenerated kubernetes self signed certificate, and not that pointed in configuration. Somebody had such a problem?
Hi, what was the solution?
Hi, I think that it is the installation binaries files problem (23.2.6). I will try today with newest (24.1.2)
I used correct files but still got the issue and the issue was resolved by generating the ‘.pfx’ file using the below algorithm,
openssl pkcs12 -export -out xxx.pfx -inkey xxx.key -in xxx-ca.cer -passout pass:xxx -certpbe PBE-SHA1-3DES -keypbe PBE-SHA1-3DES -macalg sha1
+14CgiTomasG wrote:
Darshana Herath wrote:
CgiTomasG wrote:
Hi,
I’m trying to update SSL certificate for IFS CLOUD 24.1 and the application is always signt by old certificate. I tried relative path, full path, set file as script parameter in cli and nothing worked. I deleted kubernetes cluster and installed it again, but now application is signed by autogenerated kubernetes self signed certificate, and not that pointed in configuration. Somebody had such a problem?
Hi, what was the solution?
Hi, I think that it is the installation binaries files problem (23.2.6). I will try today with newest (24.1.2)
Got a New issue.
It shows the updated certificate in management serve, but old certificate while trying from laptop (cache cleared)
Darshana Herath wrote:
CgiTomasG wrote:
Darshana Herath wrote:
CgiTomasG wrote:
Hi,
I’m trying to update SSL certificate for IFS CLOUD 24.1 and the application is always signt by old certificate. I tried relative path, full path, set file as script parameter in cli and nothing worked. I deleted kubernetes cluster and installed it again, but now application is signed by autogenerated kubernetes self signed certificate, and not that pointed in configuration. Somebody had such a problem?
Hi, what was the solution?
Hi, I think that it is the installation binaries files problem (23.2.6). I will try today with newest (24.1.2)
I used correct files but still got the issue and the issue was resolved by generating the ‘.pfx’ file using the below algorithm,
openssl pkcs12 -export -out xxx.pfx -inkey xxx.key -in xxx-ca.cer -passout pass:xxx -certpbe PBE-SHA1-3DES -keypbe PBE-SHA1-3DES -macalg sha1
Thank you, that fixed problem with certificate installation.
1 person likes this
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.