Have this working locally with tpsclient. Patch nearly ready for review.

Previous patch was approved.

Further progress on this:

Researched the problem with esc talking to the new TPS. There were a couple of issues:

1. The client was putting a line feed in the initial http chunked encoded request like this:

POST /tps/tps
HTTP 1.1

Well, it looks like tomcat doesn't like that. It expects this:

POST /tps/tps HTTP 1.1

This required a simple fix the esc's http library to make sure that stray lf does not show up in the string.

1. Once that was working then there were some minor issues on the back end to deal with.
   • The server code we have was adding an extra "chunk size" value before the chunked message.
     We were trying to emulate chunked encoding in our own code but it turns out if tomat gets a message with the Transfer-Encoding : chunked header from the client it knows what to do to send back the answer. Here we just give it the raw message to send back and the filters take care of all this.

Once all that was resolved locally, I was able to attempt a format with an old egate token (for safety) and get the secure channel to succeed just like we have been doing with tpsclient.

Before submitting this patch I want to go back and make sure that tpsclient still works with the latest changes t how messages are read and written to the steam.

Once this is all approved and checked in, we can close this ticket and move on.

Lastest patch for this allows a Gemalto 64 K token to get a secure channel.

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/1441

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.