sssd-secrets claims to support http and https proxies. However https does not actually talk TLS/SSL. According to Wireshark it sends plain HTTP.
[sssd] services = nss domains = local config_file_version = 2 [domain/local] id_provider=local [secrets] debug_level = 1310 timeout = 3000 [secrets/users/0] provider=proxy proxy_url = https://localhost:10443/secrets/
In my opinion sssd-secrets should not offer plain http at all. Instead it should only support https for remote servers and http+unix for local servers. Since HTTPS is rather complicated libcurl might be a good option. libcurl can perform HTTP over Unix, custom CA certs and TLS client cert authentication -- all features I'd like to see in sssd-secrets.
Christian, do you see this as more of a nice to have or required for some of the integration work you are doing? Just trying to figure out the best milestone here..
I see HTTPS support as a requirement for production use. HTTP is only good enough for a product demo or proof-of-concept. IMHO sssd-secrets should not support plain HTTP in the first place.
HTTPS support with optional client cert authentication would make my integration work a bit easier. Custodia pulls in Python and several additional dependencies. The sssd secrets service provides a lightweight proxy.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.15 Beta
rhbz: => todo
priority: major => critical
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1398701
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1398701 1398701]
owner: somebody => pbrezina status: new => assigned
milestone: SSSD 1.16 Beta => SSSD 1.15.1
priority: critical => major
Metadata Update from @cheimes: - Issue assigned to pbrezina - Issue set to the milestone: SSSD 1.15.1
Since we are releasing 1.15.1 today, I'm moving all unfinished tickets from 1.15.1 to 1.15.2
Metadata Update from @jhrozek: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue close_status updated to: None
Metadata Update from @jhrozek: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset
Metadata Update from @jhrozek: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue set to the milestone: SSSD 1.15.2 (was: SSSD 1.15.1)
Metadata Update from @jhrozek: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)
master:
Metadata Update from @lslebodn: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
Metadata Update from @lslebodn: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4225
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.