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.

Sign up for GitHub

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

Jump to bottom

CTN: obtain client's username from both CA certs and the client cert #491

Merged
merged 1 commit into from
Jul 4, 2024
Merged

CTN: obtain client's username from both CA certs and the client cert #491

merged 1 commit into from
Jul 4, 2024

Conversation

Roytak
Copy link
Collaborator

@Roytak Roytak commented Jul 4, 2024

Before this commit cert-to-name tried to obtain the client's username solely from the client's certificate. With this commit the CA certs used to verify the client cert are also used.

session server tls UPDATE username from CA certs
668921b 
Before this commit cert-to-name tried to obtain the client's username
solely from the client's certificate. With this commit the CA certs used
to verify the client cert are also used.
@Roytak Roytak linked an issue Jul 4, 2024 that may be closed by this pull request
cert-to-name algo is picking rfc822-name from client.crt instead of ca.crt CESNET/netopeer2#1596
Open
@michalvasko michalvasko merged commit 7251b0d into CESNET:devel Jul 4, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@michalvasko michalvasko michalvasko approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

cert-to-name algo is picking rfc822-name from client.crt instead of ca.crt
2 participants
@Roytak @michalvasko