APIGEE X JAVA Callout try to initialize satatic class

[yahyaoui]

Hello,

I'm developing a java jar that validates SAMLResponse "signature" and "decryption".  I used "onelogin lib".

When running, I got this error message 

{
    "fault": {
        "faultstring": "Failed to execute JavaCallout. Could not initialize class com.onelogin.saml2.util.Util",
        "detail": {
            "errorcode": "steps.javacallout.ExecutionError"
        }
    }
}

On my local environment, my code is working.

For the build, i used to ways :

• import dependencies on my shared flow next to the jar
• add the dependecies inside the jar 

==> i got the same error message

[dchiesa1]

See this response to a different question on Friday. 

It is likely that Apigee is disallowing the onelogin JAR because of permissions errors.  You should be able to check that if you surround the logic in your execute() method with a try...catch, and then emit context variables documenting the exception. 

There are 2 possible workarounds:

1. host that logic elsewhere, outside of the Apigee gateway - like in a CloudRun instance, that is reachable via ExternalCallout. 
2. re-engineer the Java logic so that it does not depend on the onelogin JAR (and thus will avoid the permissions error)

Another question  - Have you tried using the ValidateSAMLAssertion policy that is builtin to Apigee?  If so, why is that policy not suitable for your purposes?

[dchiesa1]

yahyaoui, any response?

[yahyaoui]

Hello,

thanks for your reply !

 the ValidateSAMLAssertion policy   covers only one use case (A signed SAML Response with a signed Assertion).

On my case, i have a signed SAML Response with an encrypted Assertion. I chose the second option (re-engineer the Java logic).

I’ll let you know when I finish the redesign of the new jar.