12 Sep
2014
12 Sep
'14
10:24 p.m.
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