From 7747b9ab6dd4563b5a80a52ce0a39db51ccec346 Mon Sep 17 00:00:00 2001
From: Justin Richer <jricher@mitre.org>
Date: Tue, 3 Dec 2013 13:28:30 -0800
Subject: [PATCH] Updated Client configuration (markdown)

---
 Client-configuration.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Client-configuration.md b/Client-configuration.md
index 21acf8e..4c8962f 100644
--- a/Client-configuration.md
+++ b/Client-configuration.md
@@ -76,7 +76,7 @@ It is configurable for use in different modes through the use of different prope
 To validate ID token signatures, the client will need access to a validator for each issuer's key set. This service bean will automatically fetch the keys and set up a validator:
 
 ```
-<bean id="validatorCache" class="org.mitre.jwt.signer.service.impl.JWKSetSigningAndValidationServiceCacheService" /> 
+<bean id="validatorCache" class="org.mitre.jwt.signer.service.impl.JWKSetCacheService" /> 
 ```
 
 Depending on how the component scan is set up in the project, the validator may need to get set up as a property on the filter: