Clément Denis

More recent Jetty versions (the one currently used by Google App Engine Standard for Java 8) will fail with a slightly different error (415 instead of 501) `org.eclipse.jetty.http.BadMessageException: 415: Unsupported...

@bnasslahsen I pushed #2511 to fix this.

I've implemented a working solution here: https://github.com/okta/okta-sdk-java/compare/master...clementdenis:okta-sdk-java:external_jwt_signing It's a bit hacky, as it overrides jjwt's DefaultJwtBuilder to provide a custom JWT signer: https://github.com/clementdenis/okta-sdk-java/blob/8991e68bced31d99d3b69be23618db27d2f36560/impl/src/main/java/com/okta/sdk/impl/oauth2/AccessTokenRetrieverServiceImpl.java#L146-L151 The best solution would probably be to...

I got the same issue , here is a redacted sample JSON (the problem is with currentValue in jobRunrDashboardProgressBar-*): ```json { "version": 6, "jobSignature": "...", "jobName": "...", "amountOfRetries": 1, "labels":...

I'm using the OSS version.

This is still broken in latest versions for source jars (both in v1.0 and beta versions), the sources are in the generated folder.

The use case is to have more generic IaC code, regardless of the presence / absence of optional fields: as Terraform does not support leaving out null field when serializing...