1. Under CA connector,
    "+This property contains the URI to contact TKS for the operation <op>."
I think you meant "...contact CA..." not "...contact TKS..."
2. For CA connector, I should have provided instruction on how to configure revocation routing.
     a. add past signing CA's cert nickname as such (the CA's signing cert should already be in the nss db and trusted):
           tps.connector.ca<n>.caNickname=<signing ca nickname>
     b. when the first revocation is triggered, you might notice a new parameter added to the config, which is the automated generated Base64 encoded CA SKI. e.g.
            tps.connector.ca1.caSKI=a/OJajZmIucFjKQa4rJxvvUZmBo=
3. You probably want to remove the old conn stuff: conn.xxx
4. Maybe create a separate ticket...per discussion on irc, we want to create a "main man page" that lists out all man page key words one can man for our product. This is so that people know where to look for info now that they are gone from CS.cfg. Once created, we should put a one line that points them to the main man page to look for info, perhaps in CS.cfg's, admin ui's, cli's etc.

thanks,
Christina

On 04/23/2014 10:55 PM, Endi Sukma Dewata wrote:

The TPS connector docs in the CS.cfg have been converted into
pki-tps-connector manual page. The build scripts have been updated
accordingly.

Ticket #890, #950.
_______________________________________________
Pki-devel mailing list
Pki-devel@redhat.com
https://www.redhat.com/mailman/listinfo/pki-devel