Bug 51613 - Integration PKI S/MIME via OpenXPKI as App
Integration PKI S/MIME via OpenXPKI as App
Status: NEW
Product: UCS
Classification: Unclassified
Component: Third party
UCS 5.0
All Linux
: P3 enhancement (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
http://openxpki.readthedocs.io/en/lat...
:
Depends on: 1565 10539 10540 10541 10542 14193 45602
Blocks:
  Show dependency treegraph
 
Reported: 2020-07-05 09:04 CEST by Nico Stöckigt
Modified: 2020-07-05 09:04 CEST (History)
4 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017102621000121
Bug group (optional): Release Goal
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Stöckigt univentionstaff 2020-07-05 09:04:33 CEST
In some environments this is still a key feature und I suggest again to provide a solution.

+++ This bug was initially created as a clone of Bug #45602 +++

+++ This bug was initially created as a clone of Bug #1565 +++
> 
> Eine mittelfristige Kundenanforderung besteht darin, mit UCS PKIs aufbauen zu
> können (Zertifikate im LDAP) und damit S/MIME für E-Mail zu unterstützen. 
> 
> Bevor wir das tun, sollten wir uns genau existierende Implementierungen (z.B.
> von Microsoft oder in Sphynx / Ägypten) ansehen.

There is a solution out there to build a PKI and use a Directory Service like Samba/AD or OpenLDAP to administer S/MIME certificates for eMail. This seems to be "an old dream" and nowadays it is a quite command requirement for a company DC with Active Directory compatibility.