[java-oidc-common] branch main updated: JCOMOIDC-10 - Bump OIDC-SDK to v9 from 8.33.1

[Phil Smart]

This is an automated email from the git hooks/post-receive script.

philsmart pushed a commit to branch main
in repository java-oidc-common.

View the commit online:
http://git.shibboleth.net/view/?p=java-oidc-common.git;a=commit;h=dd268f91b4bd02438815256332937d93d14bd065

The following commit(s) were added to refs/heads/main by this push:
       new  dd268f9   JCOMOIDC-10 - Bump OIDC-SDK to v9 from 8.33.1
dd268f9 is described below

commit dd268f91b4bd02438815256332937d93d14bd065
Author: Phil Smart <philip.smart at jisc.ac.uk>
AuthorDate: Tue Feb 2 11:10:29 2021 +0000

    JCOMOIDC-10 - Bump OIDC-SDK to v9 from 8.33.1
    
    - Bump deps
    - Fix changes
    
    https://issues.shibboleth.net/jira/browse/JCOMOIDC-10
---
 .../src/main/java/net/shibboleth/oidc/jwk/support/RemoteJwkUtils.java | 3 ++-
 .../oidc/security/jwt/claims/impl/ChainingJWTClaimsValidation.java    | 2 +-
 pom.xml                                                               | 4 ++--
 3 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/oidc-common-crypto-api/src/main/java/net/shibboleth/oidc/jwk/support/RemoteJwkUtils.java b/oidc-common-crypto-api/src/main/java/net/shibboleth/oidc/jwk/support/RemoteJwkUtils.java
index 6ab08cd..1beec43 100644
--- a/oidc-common-crypto-api/src/main/java/net/shibboleth/oidc/jwk/support/RemoteJwkUtils.java
+++ b/oidc-common-crypto-api/src/main/java/net/shibboleth/oidc/jwk/support/RemoteJwkUtils.java
@@ -19,6 +19,7 @@ package net.shibboleth.oidc.jwk.support;
 
 import java.io.IOException;
 import java.net.URI;
+import java.util.Map;
 
 import org.apache.http.HttpResponse;
 import org.apache.http.ParseException;
@@ -90,7 +91,7 @@ public final class RemoteJwkUtils {
         log.trace("{} Fetched the following response body: {}", logPrefix, output);
         final JWKSet jwkSet;
         try {
-            final JSONObject json = JSONObjectUtils.parse(output);
+            final Map<String, Object> json = JSONObjectUtils.parse(output);
             // The following check is needed to avoid NPE from Nimbus if keys claim not found
             if (JSONObjectUtils.getJSONArray(json, "keys") == null) {
                 log.error("{} Could not find 'keys' array from the JSON from {}", logPrefix, uri);
diff --git a/oidc-common-crypto-impl/src/main/java/net/shibboleth/oidc/security/jwt/claims/impl/ChainingJWTClaimsValidation.java b/oidc-common-crypto-impl/src/main/java/net/shibboleth/oidc/security/jwt/claims/impl/ChainingJWTClaimsValidation.java
index 47588e8..9df96a9 100644
--- a/oidc-common-crypto-impl/src/main/java/net/shibboleth/oidc/security/jwt/claims/impl/ChainingJWTClaimsValidation.java
+++ b/oidc-common-crypto-impl/src/main/java/net/shibboleth/oidc/security/jwt/claims/impl/ChainingJWTClaimsValidation.java
@@ -87,7 +87,7 @@ public class ChainingJWTClaimsValidation extends AbstractInitializableComponent
             log.trace("No claims to verify, nothing todo");
             return;
         }
-        log.trace("Attempting JWT claims verification for subject '{}'",claims.getSubject());
+        log.debug("Attempting JWT claims verification for subject '{}'",claims.getSubject());
         
         for (final ClaimsValidator validator : claimValidators) {
             log.trace("Attempting JWT claims validator '{}'", validator.getId());
diff --git a/pom.xml b/pom.xml
index e4f4e89..192ea5d 100644
--- a/pom.xml
+++ b/pom.xml
@@ -20,8 +20,8 @@
 		<opensaml.groupId>org.opensaml</opensaml.groupId>
 		<opensaml.version>4.1.0-SNAPSHOT</opensaml.version>
 		<java-support.version>8.2.0-SNAPSHOT</java-support.version>
-		<nimbus-jose-jwt.version>8.20.1</nimbus-jose-jwt.version>
-        <oauth2-oidc-sdk.version>8.33.2</oauth2-oidc-sdk.version>
+		<nimbus-jose-jwt.version>9.4.1</nimbus-jose-jwt.version>
+        <oauth2-oidc-sdk.version>9.0</oauth2-oidc-sdk.version>
 		<checkstyle.configLocation>${project.basedir}/checkstyle.xml</checkstyle.configLocation>
 	</properties>
 	<repositories>

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.