13.0.2 missing UTF-8 support in Azure about okta-sdk-java HOT 4 CLOSED

So apparently the Okta SDK is sensitive to the underlying default charset. For some reason that I will be raising with Microsoft, the default charset for the jvm is US ASCII. By setting the default charset to UTF8 the values were properly decoded. I'm good now. I'll leave this to your discretion to close.

from okta-sdk-java.

@JEBailey Thanks for posting! Will check and address this.

from okta-sdk-java.

@JEBailey I checked this scenario and I find it working as expected (characters are encoded correctly).

I wrote a simple test (https://github.com/okta/okta-sdk-java/blob/master/integration-tests/src/test/groovy/com/okta/sdk/tests/it/UsersIT.groovy#L171-L193) that tests this and below is the snapshot of the debugger view:

Here's the console view:

from okta-sdk-java.

Went back and continued research. So this is apparently environment specific. When we first ran into it there was an open issue with UTF8 support and we believed this was related.

This appears to be happening only in our Azure Function container and only with the Okta SDK. We're receiving Okta web hooks with the correct encoding, we're dealing with other services where we are decoding the UTF-8 value correctly. It's only within the context of the Okta SDK where we retrieve a User that the encoding appears to break

from okta-sdk-java.