mirror of
https://github.com/lldap/lldap.git
synced 2026-04-26 00:36:01 +03:00
[GH-ISSUE #288] Support for PKCS#1 keys #106
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ajgon on GitHub (Aug 21, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/288
Hey,
I'm building a HELM file to introduce lldap to my k3s cluster as a user backend for authelia. The problem is, that
genSignedCerthelm helper, cannot customize the private keys format and arbitrarly uses PKCS#1. Since lldap uses PKCS#8, it fails to load the key.I'm not very familiar with LDAP, so I'm not sure if PKCS#8 was a lldap design decision, or just a requirement for LDAP, but is it possible to support PKCS#1 keys as well? I think it can be done without breaking the compatibility, using fallback (if pkcs8 fails, try to load as pkcs1).
This is purely QOL improvement, as I can always ask user to provide proper keys in helm config - but supporting the certificate autogeneration would be a nice addition to this :)
Edit: If anybody is interested, here is the chart on artifact hub.
@ajgon commented on GitHub (Oct 1, 2022):
Awesome, thank you for that. I updated my chart as well.