Not able to set UserProfile.secondEmail to null

[srrentgeral]

Describe the bug?

Setting UserProfile.secondEmail = null does not remove or update the field when using the Java Okta SDK (okta-sdk-api version 21.0.0). Other updates with non-null values work as expected, but attempting to set secondEmail to null does not take effect.

Use the Okta Java SDK (version 21.0.0) to update a user’s profile.
Set UserProfile.secondEmail to null.
Call the API using:
com.okta.sdk.resource.api.UserApi#updateUser(java.lang.String, com.okta.sdk.resource.model.UpdateUserRequest, java.lang.Boolean)

SecondEmail is not removed or updated in the Okta user profile.

Calling update on Okta api directly with below request works but not with java sdk
{
"profile": {
"secondEmail": null
}
}

What is expected to happen?

Setting UserProfile.secondEmail = null should remove the field or set it to null in the Okta user profile.

What is the actual behavior?

The API request is sent with UserProfile.secondEmail=null, but secondEmail remains unchanged.

Reproduction Steps?

• Use the Okta Java SDK (version 21.0.0) to update a user’s profile.
• Set UserProfile.secondEmail to null.
• Call the API using:
  com.okta.sdk.resource.api.UserApi#updateUser(java.lang.String, com.okta.sdk.resource.model.UpdateUserRequest, java.lang.Boolean)
  SecondEmail is not removed or updated in the Okta user profile.

Additional Information?

No response

Java Version

17.0.9

SDK Version

21.0.0

OS version

No response

[prachi-okta]

@srrentgeral Thank you for reporting this! I will be taking a look at this and will update.