BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
Nigel_Pain
Lapis Lazuli | Level 10

SAS 9.4M7 on Windows 2012 R2

I'm at the point of renewing certificates on our mid-tier server and have a certificate bundle ready. However, it needs exported to PKCS12 format for the webapps. I've been following the procedure that we've used before but I'm getting an error with the openssl command:

 

C:\Windows\system32>Set OPENSSL_CONF= E:\SAS\sashome\SASWebServer\9.4\httpd-2.4.27.1-64\ssl\openssl.cnf
C:\Windows\system32>e:
E:\>cd E:\SAS\sashome\SASWebServer\9.4\httpd-2.4.27.1-64\bin
E:\SAS\sashome\SASWebServer\9.4\httpd-2.4.27.1-64\bin>openssl pkcs12 -export -chain -inkey "E:\SAS\config\Lev1\Web\WebServer\ssl\keyfile.key" -in "C:\temp\Certificates\certfile.crt" -name hq -CAfile "C:\temp\Certificates\CAchain.crt" -out c:\temp\Certificates\tcServer.p12 19040:error:0200107B:system library:fopen:Unknown error:.\crypto\bio\bss_file.c:175:fopen(' E:\SAS\sashome\SASWebServer\9.4\httpd-2.4.27.1-64\ssl\openssl.cnf','rb') 19040:error:2006D002:BIO routines:BIO_new_file:system lib:.\crypto\bio\bss_file.c:184: 19040:error:0E078002:configuration file routines:DEF_LOAD:system lib:.\crypto\conf\conf_def.c:203:

I tried adding the path to the openssl command to PATH, to no avail. The certificate file is just that, ie. doesn't include the CA chain. The CA file just contains the root and intermediate certificates. I seem to have problems with this every time, and no matter how well I document the process it always goes wrong!

Suspect this might be a job for TS but just in case anyone can help? 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Nigel_Pain
Lapis Lazuli | Level 10

I've sorted it. There was a space before the beginning of the assignment of the OPENSSL_CONF environment variable. Removed that and it worked. Doh!

View solution in original post

1 REPLY 1
Nigel_Pain
Lapis Lazuli | Level 10

I've sorted it. There was a space before the beginning of the assignment of the OPENSSL_CONF environment variable. Removed that and it worked. Doh!

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 506 views
  • 0 likes
  • 1 in conversation