Skip to content
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

Gen additional Client Certs #18

Closed
nolech opened this issue Oct 28, 2019 · 9 comments · Fixed by #37
Closed

Gen additional Client Certs #18

nolech opened this issue Oct 28, 2019 · 9 comments · Fixed by #37
Assignees

Comments

@nolech
Copy link

nolech commented Oct 28, 2019

I didn't see in the documentation how to generate another client cert after the CA and server cert were already created. Is this possible?

@lukebakken
Copy link
Collaborator

This isn't currently supported, but is possible. Basically the existing data would have to be preserved. We'd be happy to review a pull request that implements this feature.

@pawel-marciniak
Copy link

Can anyone provide some help on that?

@lukebakken lukebakken reopened this Oct 31, 2019
@lukebakken
Copy link
Collaborator

@nolech @pawel-marciniak please test my branch here:

https://github.com/lukebakken/tls-gen/tree/lrb-gen-client-cert-only

In the basic profile, you can use the following command to create additional client certs using a specific common name:

make CN=client-name-2 gen-client

Look for the files in result/, they will have CN as part of the name.

@lukebakken lukebakken self-assigned this Oct 31, 2019
@pawel-marciniak
Copy link

@lukebakken Great, thanks a lot :) I will definitely give it a try today.

@tasoss
Copy link

tasoss commented Feb 19, 2020

Hello.
I suppose this hasn't been implemented yet.Right?
Is it still ok to use the given solution?

@lukebakken
Copy link
Collaborator

I'm waiting for someone else to test the changes I made on the lrb-gen-client-cert-only branch.

@mihaj
Copy link

mihaj commented Feb 5, 2021

Hi, @lukebakken. I can test the changes. Can you create a PR? It looks like your repo is not available.

@lukebakken
Copy link
Collaborator

@mihaj you're in luck. I managed to find a clone with the branch. See #31. It needs to have conflicts resolved which I don't have time to do today.

@mihaj
Copy link

mihaj commented Feb 5, 2021

Cool, let me check If I can resolve that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants