ClearFoundation Tracker - ClearOS | |||||
| View Issue Details | |||||
| 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. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2014-03-31 10:05 | user2 | New Issue | |||
| 2014-03-31 10:06 | user2 | Status | new => confirmed | ||
| 2018-09-25 12:05 | user2 | Status | confirmed => resolved | ||
| 2018-09-25 12:05 | user2 | Fixed in Version | => 7.5.0 | ||
| 2018-09-25 12:05 | user2 | Resolution | open => fixed | ||
| 2018-09-25 12:05 | user2 | Assigned To | => user2 | ||
| 2018-09-25 12:05 | user2 | Status | resolved => closed | ||
| There are no notes attached to this issue. |