This issue has been resolved in a hot fix for RSA ClearTrust 5.0.1. Contact RSA Security Customer Support to obtain hot fix 5.0.1.114, or request the latest fix level (which is cumulative, and contains fixes from previous fix levels).