[GH-ISSUE #35] Feature Request: Publish certificates to LDAP #30

Open
opened 2026-02-26 03:33:31 +03:00 by kerem · 7 comments
Owner

Originally created by @amaccuish on GitHub (Oct 20, 2017).
Original GitHub issue: https://github.com/laurivosandi/certidude/issues/35

If the user is authenticated via LDAP, it would be useful to publish the newly created certificate to the corresponding certificate attribute in Active Directory.

Originally created by @amaccuish on GitHub (Oct 20, 2017). Original GitHub issue: https://github.com/laurivosandi/certidude/issues/35 If the user is authenticated via LDAP, it would be useful to publish the newly created certificate to the corresponding certificate attribute in Active Directory.
Author
Owner

@laurivosandi commented on GitHub (Dec 27, 2017):

Hello, could you please describe a usecase for this? How do you imagine receiving CSR-s in that case?

<!-- gh-comment-id:354125035 --> @laurivosandi commented on GitHub (Dec 27, 2017): Hello, could you please describe a usecase for this? How do you imagine receiving CSR-s in that case?
Author
Owner

@amaccuish commented on GitHub (Feb 23, 2018):

The normal request process would apply, but it's useful so users can lookup certificates in Outlook for S/MIME etc.

<!-- gh-comment-id:368064190 --> @amaccuish commented on GitHub (Feb 23, 2018): The normal request process would apply, but it's useful so users can lookup certificates in Outlook for S/MIME etc.
Author
Owner

@laurivosandi commented on GitHub (Feb 23, 2018):

So you're saying you want to publish certificates issued to a particular user under the userCertificate attribute?

<!-- gh-comment-id:368146350 --> @laurivosandi commented on GitHub (Feb 23, 2018): So you're saying you want to publish certificates issued to a particular user under the userCertificate attribute?
Author
Owner

@amaccuish commented on GitHub (Feb 23, 2018):

Yes. So if someone authenticated using ldap or kerberos, we can find them in ldap and at time off issuance store the public key in ldap, overwriting usually anything that's there.

<!-- gh-comment-id:368146615 --> @amaccuish commented on GitHub (Feb 23, 2018): Yes. So if someone authenticated using ldap or kerberos, we can find them in ldap and at time off issuance store the public key in ldap, overwriting usually anything that's there.
Author
Owner

@laurivosandi commented on GitHub (Feb 25, 2018):

This should be doable with one constraint - Certidude should not remove other certificates issued by some other CA. I have currently Estonian ID-card certificates attached to the user for example so issuing another certificate from Certidude should not break that.

<!-- gh-comment-id:368339096 --> @laurivosandi commented on GitHub (Feb 25, 2018): This should be doable with one constraint - Certidude should not remove other certificates issued by some other CA. I have currently Estonian ID-card certificates attached to the user for example so issuing another certificate from Certidude should not break that.
Author
Owner

@amaccuish commented on GitHub (Feb 25, 2018):

I have the exact same. My personal account has both an Estonian ID-card certificate and a internel ca signed cert.

<!-- gh-comment-id:368339252 --> @amaccuish commented on GitHub (Feb 25, 2018): I have the exact same. My personal account has both an Estonian ID-card certificate and a internel ca signed cert.
Author
Owner

@amaccuish commented on GitHub (Feb 25, 2018):

Maybe include some logic to replace only certificates issued by itself?

<!-- gh-comment-id:368339306 --> @amaccuish commented on GitHub (Feb 25, 2018): Maybe include some logic to replace only certificates issued by itself?
Sign in to join this conversation.
No labels
pull-request
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/certidude-laurivosandi#30
No description provided.