-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which files for starting Step #9 #2
Comments
I am not sure where these files came from for step #9: openssl x509 -req -days 365 -in identity.csr -CA cacert.crt -CAkey cakey.key -CAcreateserial -out identity.crt |
When I download our CA Cert from GoDaddy ... It comes with 2 files - both .crt. One is a single and one is a bundle. Where and how do I generate the identity.csr and the other 3 .key files? |
One of them must contain the content of all 3 files. You can open these file in any text editor. Certificate Authority (CA) content will look like this
Certificate Signing Request (CSR) content will look like this
SSL certificate private key content will look like this
|
Sorry - just to clarify. One of the 2 files that I download comes with 1 cert in it. This is the file CA Cert that I duplicate into three copies of files named cacert.crt, identity.crt and server.crt. Then the other .crt file that has the "bundle" in the filename - that I piece out the indetity.csr file from the section above, and then the other section that has the SSL private keys I part out and make those cakey.key, server.key and identity.key? The directions above weren't super clear. |
Yes, because different platform manages SSL certificate differently, that's why I added the content of the different certificate file. BTW, thanks for clarifying. Someone may find this helpful who is using GoDaddy. Also, you can write the Step 9 for GoDaddy. I'll add that in my article. 😄 |
It might be helpful to write up directions for a brand new cert as the rest
of your directions have been spot on.
Spencer
…On Wed, Sep 5, 2018 at 11:14 PM Vineet Choudhary ***@***.***> wrote:
Yes, because different platform manages SSL certificate differently,
that's why I added the content of the different certificate file.
BTW, thanks for clarifying. Someone may find this helpful who is using
GoDaddy.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB0TcsszSOAUC4ekn0f9ct5jPQnQ_bJoks5uYL0vgaJpZM4WaN3o>
.
|
Yes, that will be helpful if you are a full stack developer. But in most of the case, these certificate managed by backend developer. |
@vineetchoudhary is it possible to use self-signed SSL-certificates for the server? Will it work? |
Hi @ulian-onua, Yes, you can use self-signed SSL-Certificates. |
@vineetchoudhary thank you |
In step #9:
"Go to the scripts directory and rename the different part of your domain SSL certificate as following -
Rename your Certificate Authority (CA) certificate to cacert.crt, identity.crt and server.crt (Same file with three different name). Your CA cetificate content looks like this ..."
What file is the CA cert? Which file from steps 1-8 are we renaming to the same 3 files?
Are we supposed to run this script to create the files first: https://github.com/intrepidusgroup/imdmtools/blob/master/Tools/server/certs/make_certs.sh
The text was updated successfully, but these errors were encountered: