Anonymous | Login | 2024-11-21 01:46 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0001642 | ClearOS | app-certificate-manager - Certificate Manager | public | 2014-03-31 10:05 | 2018-09-25 12:05 | ||||
Reporter | user2 | ||||||||
Assigned To | user2 | ||||||||
Priority | normal | Severity | tweak | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | 7.5.0 | |||||||
Summary | 0001642: Use only a single organization in certificates | ||||||||
Description | Multiple organizations are permitted in certificates, but it has been reported to be problematic by a client (no details given). Regardless, it's probably best just to have a single organization. In the openssl.cnf file, the following exists: 0.organizationName = ClearOS And when a user generates a certificate, the user-specified organization is added: ... snip ... 0.organizationName = ClearOS organizationName = UsersOrg ... snip ... This does not seem to cause problems with web browser (Chrome, Firefox, IE, etc), Zarafa, and various LDAP clients, but perhaps some clients don't like it. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||