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

libserdes self signed certificate path #7

Closed
pranmod opened this issue Mar 13, 2018 · 6 comments · May be fixed by #41
Closed

libserdes self signed certificate path #7

pranmod opened this issue Mar 13, 2018 · 6 comments · May be fixed by #41
Labels
enhancement

Comments

@pranmod
Copy link

pranmod commented Mar 13, 2018

Hi how do we specify selfsigned certificate path to libserdes to be used during schema server registration. I see from code it is using REST_POST but not taking certificate path as part of any of these APIs serdes_conf_new() and serdes_schema_add(). My schema registration is failing with following error "Failed to register schema name: - REST request failed (code -1): HTTP request failed: Peer certificate cannot be authenticated with given CA certificates"
@edenhill
Copy link
Contributor

edenhill commented Mar 14, 2018 •
edited
Loading

It is using the system's default CA path location, but it does make sense to allow specifying an alternate path for self signed certs.

What we need to do is expose a new ssl.ca.location configuration property that maps to CURL_CAPATH.

@pranmod
Copy link
Author

pranmod commented Mar 14, 2018

Yes that would help. This is similar to how librdkafka is taking a SSL certificate path. When can we have this change?

@edenhill
Copy link
Contributor

I can whip up a PR for you to try out next week.

@pranmod
Copy link
Author

pranmod commented Mar 28, 2018

Hi Eden, do you have changes ready for this for me try it out.

@pranmod
Copy link
Author

pranmod commented Apr 5, 2018

Hi Can you please let me know when this changes be available?

beeender added a commit to beeender/libserdes that referenced this issue Apr 14, 2021
@beeender
Add support for SSL registry
0fd6bc9 
- Add option 'ssl.ca.location', 'ssl.certificate.location',
  'ssl.key.location' and 'ssl.enabled.min_protocol' to support SSL
  enabled registry service.

Limitations:
- 'schema.registry.url' accepts multiple URLs separated by ','. But
  the options added by this commit don't. That means all the URLs will
  use the same SSL information provided by those options.

Close confluentinc#7
@beeender beeender mentioned this issue Apr 14, 2021
Open
@alecbcs
Copy link

alecbcs commented Jan 23, 2024

@edenhill can we reopen this issue? The PR linked doesn't appear to be merged yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for SSL registry beeender/libserdes
3 participants
@edenhill @alecbcs @pranmod