{"push_id":2364069749,"size":1,"distinct_size":1,"ref":"refs/heads/DOGTAG_10_5_BRANCH","head":"7f4eae3c78daf8d56b76153e3f48086a804c3d3d","before":"ea7085a33fc6573eaed3e7775f40704ce12384da","commits":[{"sha":"7f4eae3c78daf8d56b76153e3f48086a804c3d3d","author":{"name":"Christina Fu","email":"8d7edf654be82002a8e01940ff22b9ea868c4661@redhat.com"},"message":"Ticket #2949 CMCAuth throws org.mozilla.jss.crypto.TokenException: Unable to insert certificate into temporary database\n\nThis patch addresses the \"TokenException: Unable to insert certificate into temporary database\" issue caused by CMC authentication.  During the CMC authentication, looks like the following JSS CryptoManager call actually tries to import the certificate temporarily into the token and causes conflicts:\npublic boolean isCertValid(byte[] certPackage, boolean checkSig,\n            CertUsage certUsage)\nThat call is not appropriate for the purpose.\n\nLooking closely,  certificate validation has been done in various places:\n* SSL client authentication (if used)\n* the isRevoked() call either in agent authentication or in CMCUserSignedAuth\n* the cert.checkValidity() call in CMCUserSignedAuth\n\nThe extra isCertValid call is not only redundant but also problematic.\n\nThis patch fixes https://pagure.io/dogtagpki/issue/2949\n(cherry picked from commit c6630a429f6f4a9b2c2090001f0a2c50e10ba5c4)\n\nChange-Id: I47367b02c8a53a9cfa99b5da370a3a6af1cb9676","distinct":true,"url":"https://api.github.com/repos/dogtagpki/pki/commits/7f4eae3c78daf8d56b76153e3f48086a804c3d3d"}]}
{"actor":{"display_login":"mharmsen99"}}