[GH-ISSUE #288] Support for PKCS#1 keys #106

Closed
opened 2026-02-27 08:15:16 +03:00 by kerem · 1 comment
Owner

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 genSignedCert helm 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.

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 `genSignedCert` helm 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](https://artifacthub.io/packages/helm/ajgon/lldap).
Author
Owner

@ajgon commented on GitHub (Oct 1, 2022):

Awesome, thank you for that. I updated my chart as well.

<!-- gh-comment-id:1264337205 --> @ajgon commented on GitHub (Oct 1, 2022): Awesome, thank you for that. I updated [my chart](https://artifacthub.io/packages/helm/ajgon/lldap/0.4.0) as well.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#106
No description provided.