[PATCH] 275 Fixed token authentication problem on RHEL.
The CryptoManager.initialize() and CryptoToken.login() invocation has been moved into the main program as a workaround for the authentication problem on RHEL and to ensure proper initialization in general. Bugzilla #985111 -- Endi S. Dewata
ACK: Just a quick question though. Was there a reason not to create another initCertDB method for the new class the code was moved to, instead of putting it inline? ----- Original Message ----- From: "Endi Sukma Dewata" <edewata@redhat.com> To: "pki-devel" <pki-devel@redhat.com> Sent: Wednesday, July 17, 2013 9:37:13 AM Subject: [Pki-devel] [PATCH] 275 Fixed token authentication problem on RHEL. The CryptoManager.initialize() and CryptoToken.login() invocation has been moved into the main program as a workaround for the authentication problem on RHEL and to ensure proper initialization in general. Bugzilla #985111 -- Endi S. Dewata _______________________________________________ Pki-devel mailing list Pki-devel@redhat.com https://www.redhat.com/mailman/listinfo/pki-devel
On 7/22/2013 5:02 PM, John Magne wrote:
ACK:
Just a quick question though. Was there a reason not to create another initCertDB method for the new class the code was moved to, instead ofputting it inline?
It could be done that way, but it's not necessary because for now the code will only be called by MainCLI. The MainCLI.init() doesn't contain a lot of stuff so I thought I'd just put it in there. Ideally, once the actual problem is fixed I'd like to restore the PKIClient.initCertDatabase() so it can be reused by other programs. Pushed to master and 10.0.x branch. Thanks. -- Endi S. Dewata
participants (2)
-
Endi Sukma Dewata -
John Magne