[Pki-devel] [PATCH] pki-cfu-0036-ticket-1158-CMCRequest-does-not-support-internal-tok.patch

John Magne jmagne at redhat.com
Tue Sep 16 18:01:18 UTC 2014


ACK

Looks like we have feature parity with the others tools.

If tested to work. Good.

----- Original Message -----
From: "Christina Fu" <cfu at redhat.com>
To: pki-devel at redhat.com
Sent: Friday, September 12, 2014 3:24:10 PM
Subject: [Pki-devel] [PATCH]	pki-cfu-0036-ticket-1158-CMCRequest-does-not-support-internal-tok.patch

It seems the CMCRequest java tool initializes its token to be hardcoded 
as "internal".  In case when -h is not specified, it will attempt to do 
getTokenByName and will get a token not found error.
I checked all the other java tools they initialize tokenname to be null, 
and properly calls getInternalKeyStorageToken from jss CryptoManager.

This fix allows CMCRequest to now work with internal token.

Please review.
thanks,
Christina

_______________________________________________
Pki-devel mailing list
Pki-devel at redhat.com
https://www.redhat.com/mailman/listinfo/pki-devel




More information about the Pki-devel mailing list