File based certificate fall-back caches returning incorrect certificates.

What steps will reproduce the problem?
1. In some instances, the file based cert caches are returning old certificates 
that never expire for either an organization or user.
2.
3.

What is the expected output? What do you see instead?
File based fall back caching = serves little value due to it's implementation 
and is generally mitigated with in memory caching.

The file based cache will be disabled by default in the gateway.  I would 
prefer to remove it completely from the resolvers, but for passivity reasons it 
needs to be able to support those that have implemented their own file based 
caches.

Original issue reported on code.google.com by gm2...@cerner.com on 8 Jun 2012 at 11:47

ronysebastian / nhin-d

File based certificate fall-back caches returning incorrect certificates. #184