-
Notifications
You must be signed in to change notification settings - Fork 14
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
creating intermediate ca signed by an external root #30
Comments
I am assuming you are working with the REST API? First you'll want to hit When you send your payload to create an intermediate CA, you want to set The result should then be that the intermediate CA is generated and signed at this point. |
I tried to use an external root for the intermediate cert. I tried to replace the pki files for the intermediate CA with files from a valid sub-CA, signed by an external root, but all I have now is "error 500" |
I do not believe using an external CA is a currently supported use case. |
The current use case of intermediate CA is when you are the CA admin and want to delegate an intermediate CA. |
Thanks for making it clear! |
I don't understand the concept of creating an intermediate ca.
In my understanding, it should create a full CA, but instead of the ca.crt, a csr should be created, and after getting it signed with the root-CA, the ca.crt should be uploaded. it works this way using easy-rsa f.e.
here, when I create a ca with "intermediate": true, and "parent_common_name" added, the resulted CA data will contain only keys, and "isIntermediate": false
It's my issue tbh, but how this flow supposed to work?
The text was updated successfully, but these errors were encountered: