#2672 Banner.txt should only accept file type UTF-8 Unicode text and ASCII text
Closed: duplicate 6 years ago Opened 6 years ago by mharmsen.

Application should accept Banner.txt only when file type is UTF-8 Unicode text
and ASCII text

Steps to Reproduce:

1.move the content of binary file into banner.txt
2.run pki command

Actual results:

error occurs as below
root@server6 ~ # pki -d /root/multihost_tests/certdb/ -c Secret123 -h
pki1.example.com -p 20080 -n "PKI CA Administrator for Example.Org" user-del
tuser1
JAXBUnmarshalException: javax.xml.bind.UnmarshalException
- with linked exception:
[org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 83; An invalid XML
character (Unicode: 0x3) was found in the element content of the document.]

Expected results:

file type can be determined and only ASCII and UTF-8 can be allowed.

root@pki1 ~ # file /etc/pki/pki-tomcat/banner.txt
/etc/pki/pki-tomcat/banner.txt: UTF-8 Unicode text, with very long lines

root@pki1 ~ # file /etc/pki/pki-tomcat/banner.txt
/etc/pki/pki-tomcat/banner.txt: ASCII text

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

6 years ago

Moving to N/A as this ticket was accidently created twice using IPA Ticket Tool

Metadata Update from @mharmsen:
- Issue set to the milestone: N/A (was: 10.4)

6 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2792

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata