History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JM-1204
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Gaston Dombiak
Reporter: Gaston Dombiak
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Openfire

Certificate Signing Requests are not generated when issuer name matches xmpp domain

Created: 12/10/07 05:47 PM   Updated: 12/18/07 01:01 PM
Component/s: Admin Console
Affects Version/s: 3.4.2
Fix Version/s: 3.4.3

Time Tracking:
Not Specified

Support Plan Customer Issue: No
Resolution Date: 12/18/07 01:01 PM
Acceptance Test - Add?: No


 Description  « Hide
Certificate Signing Requests are not generated when issuer name matches xmpp domain. To reproduce this problem create new certificates and then complete the issuer information from the admin console. When entering the Name of the issuer use the XMPP domain of the server. Once saved you will go back to the certificates page but you won't be able to get the CSR information.

Both ssl-signing-request.jsp and ssl-certificates.jsp have a line like this:

// Self-signed certs are certs generated by Openfire whose IssueDN equals SubjectDN
boolean isSelfSigned = c.getSubjectDN().equals(c.getIssuerDN());

The problem is subjectDN was modified for 3.4.2 to be like issuerDN to be accepted by some CAs. We now need to use another logic to find out whether a certificate is self-signed or not. Certificates created by Openfire will use CN=[domain] as the subjectDN and issuerDN. When a CSR is created both fields (subjectDN and issuerDN) are updated to include the meta data (O=,ST=, OU=,etc.).



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.