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

Make app_pki_key and app_pki_cert optional #141

Closed
virus2500 opened this issue Nov 28, 2023 · 4 comments
Closed

Make app_pki_key and app_pki_cert optional #141

virus2500 opened this issue Nov 28, 2023 · 4 comments

Comments

@virus2500
Copy link
Contributor

Hi,

we don't use Client certificate authentication and failed to connect to our openldap since it apparently always uses client authentication as the mechanism.

When we commented out the lines

  # if $app_pki_key {
  #   $ldap_tls_key = $app_pki_key
  # } else {
  #   $ldap_tls_key = "${sssd::app_pki_dir}/private/${$facts['fqdn']}.pem"
  # }

  # if $app_pki_cert {
  #   $ldap_tls_cert = $app_pki_cert
  # } else {
  #   $ldap_tls_cert = "${sssd::app_pki_dir}/public/${$facts['fqdn']}.pub"
  # }

from manifests/provider/ldap.pp everything started working as expected.
Looking around for this issue i also found this issue https://simp-project.atlassian.net/jira/software/c/projects/SIMP/issues/SIMP-10741

Could you make this two parameters optional. Default seems to be "not set" anyway?

TIA

@sabo
Copy link
Contributor

sabo commented Nov 29, 2023

I've submitted a PR that resolves this issue (#137) but it's been awaiting review for a while now.

@virus2500
Copy link
Contributor Author

Hi @sabo,

oops, seems like my brain didn't connect the dots while looking through the PRs.

I was thinking about how to do this without breaking their current logic.
Seems like your way is the only one that would keep their logic intact while still being able to opt-out of this behavior.

Now it would be interesting to know wether the dev(s) prefer to do it the "default" way, which would be an opt-in or keep the current way and implement your opt-out strategy.

I'll keep this issue open for now to increase visibility of this issue.

@michael-riddle michael-riddle moved this from New to Todo in Org Triage Dec 4, 2023
@sabo
Copy link
Contributor

sabo commented Nov 22, 2024

The PR mentioned above (#137) has been merged so I believe this issue can be closed.

@virus2500
Copy link
Contributor Author

Can verify it is working now. Thx everyone!

@github-project-automation github-project-automation bot moved this from Todo to Done in Org Triage Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants