Revocation Policy Failure with Redis Persistence

[shev-pro]

The revocation policy (revoked-status-list) fails when using Redis as the persistence backend in the waltid-verifier service.

Steps to Reproduce

1. Configure waltid-verifier to use Redis as the persistence backend.
2. Execute a verification request using the provided Swagger example (Example with VP & global VC policies):

curl -X 'POST' \
  'http://127.0.0.1:7003/openid4vc/verify' \
  -H 'accept: */*' \
  -H 'authorizeBaseUrl: openid4vp://authorize' \
  -H 'responseMode: direct_post' \
  -H 'Content-Type: application/json' \
  -d '{
  "vp_policies": [
    {
      "policy": "minimum-credentials",
      "args": 2
    },
    {
      "policy": "maximum-credentials",
      "args": 100
    }
  ],
  "vc_policies": [
    "signature",
    "expired",
    "not-before",
    "revoked-status-list"
  ],
  "request_credentials": [
    {
      "format": "jwt_vc_json",
      "type": "OpenBadgeCredential"
    },
    {
      "format": "jwt_vc_json",
      "type": "VerifiableId"
    }
  ]
}'

Expected Behavior

The service should return a 200 OK response with the expected verification results.

Actual Behavior

The request fails with a 400 Bad Request error and the following exception:

{"exception":true,"id":"SerializationException","status":"Bad Request","code":"400",
"message":"Serializer for subclass 'LocationIgnorantKLogger' is not found in the polymorphic scope of 'KLogger'. 
Check if class with serial name 'LocationIgnorantKLogger' exists and serializer is registered in a corresponding SerializersModule. 
To be registered automatically, class 'LocationIgnorantKLogger' has to be '@Serializable', and the base class 'KLogger' has to be sealed and '@Serializable'."}

Environment

• Docker Prebuilt Images
• WaltID Identity Version: 0.12.0

Stack Trace

(Full stack trace is attached in the issue description.)
stacktrace.txt

Possible Solution

Modify the RevocationPolicy implementation to prevent the logger from being serialized:

In waltid-libraries/credentials/waltid-verification-policies/src/jvmMain/kotlin/id/walt/policies/policies/RevocationPolicy.jvm.kt, move the following logger declaration inside the functions to ensure it is re-created per invocation and excluded from serialization:

private val logger = KotlinLogging.logger {}

This adjustment ensures that the logger does not interfere with serialization when using Redis as the persistence backend.

[alegomes]

Is it too much to ask for a PR, @shev-pro ? 🤗

[shev-pro]

Here it is: PR #996. The fix turned out to be quite straightforward.