Protect Against Any Token Parsing Failure

Previously, we only protected against the possibility that a parsed token
wasn't really a JWT token at all.  This lead us into the situation where debug
logging a token that was invalid (e.g. had already expired) would crash the
entire system.  Since logging (especially debug logging), should never be
terminal this change updates the code to protect against all parsing failures
and simply truncate logging instead of crashing the system.

[#569]

Author: nebhale

cloudfoundry-client-reactor/src/main/java/org/cloudfoundry/reactor/tokenprovider/AbstractUaaTokenProvider.java

@@ -18,7 +18,6 @@
 
 import io.jsonwebtoken.Claims;
 import io.jsonwebtoken.Jwts;
-import io.jsonwebtoken.UnsupportedJwtException;
 import io.netty.util.AsciiString;
 import org.cloudfoundry.reactor.ConnectionContext;
 import org.cloudfoundry.reactor.TokenProvider;
@@ -145,7 +144,7 @@ private static Optional<Claims> parseToken(String token) {
         try {
             String jws = token.substring(0, token.lastIndexOf('.') + 1);
             return Optional.of(Jwts.parser().parseClaimsJwt(jws).getBody());
-        } catch (UnsupportedJwtException e) {
+        } catch (Exception e) {
             return Optional.empty();
         }
     }