Red Hat Bugzilla – Bug 476736
Make ESC to TPS communication IPv6 enabled
Last modified: 2015-01-04 18:35:23 EST
Description of problem:
ESC uses its own HTTP library based on NSS and NSPR to communicate with the TPS when performing token operations. We want to make the minor change required to support IPv6 for this communication.
Version-Release number of selected component (if applicable):
Created attachment 349024 [details]
Patch to allow ESC to connect over Ipv6.
attachment (id=349024) +mharmsen
$ cvs -d :ext:email@example.com:/cvs/dirsec commit -m Bugzilla #47
6736 - Make ESC to TPS communication IPv6 enabled."
cvs commit: Examining .
Enter passphrase for key '/home/jack/.ssh/id_rsa':
Checking in httpClientNss.cpp;
/cvs/dirsec/esc/src/lib/NssHttpClient/httpClientNss.cpp,v <-- httpClientNss.c
new revision: 1.4; previous revision: 1.3
This problem should be resolved in the next build of ESC.
1. Make sure ESC is running on a machine that is Ipv6 compatible.
2. Make sure TPS/CA/TKS and DRM are running on a Ipv6 compatible host. It would be fine to have the Linux ESC running on the same host.
3. Make sure that the Ipv6 compatible JSS is installed on the host where the CS subsystems are to be installed. Also make sure TPS is listening on an IPv6 socket. /sbin/lsof -i6 . Then search for port 7888.
4. Put an entry in the machine's /etc/hosts like the following:
This gives a way for esc to accept a Ipv6 host name.
5. Run ESC and put in a blank token.
6. In the phone home dialog, put in the phone home URL , using the ipv6 name like:
7. If the phone home info is accepted, then simply try to perform a Format the token. Once ESC asks for the user authentication info, we know that we have successfully made a connection to the Ipv6 socket of TPS.
Successfully Enrolled and Formatted user token, esc running on an ipv6 enabled host following the steps in comment #4.