Openfire

Certificate generation fails when a field contains a comma

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Acceptance Test - Add?:
    Yes
  • Acceptance Test - Entry:
    1. Create new CSR in openfire server certificates page
    2. Update issuer information using fields that contain commas
    3. Verify that cert is successfully created

Description

Information fields for creating certificates in ssl-signing-request.jsp are not escaped, so if they contain a comma or other reserved character, they will fail because the tokenizer has created a new field on the comma which does not contain an "="
An error will be printed to stderr, but no error will appear in UI – after pressing update button nothing will happen (no redirect, no error)

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated: