Incorrect types for UserProfile (strings are not nullable)

[NoxHarmonium]

Describe the bug?

The UserProfile type is defined in:

https://github.com/okta/okta-sdk-nodejs/blob/master/src/types/models/UserProfile.d.ts

It has all the base/built-in profile attributes typed as non-nullable strings.

A quick call to the API via cURL shows that the Okta API can return nulls for these values.

We should probably update these types to reflect what is returned from the Okta API, so that we don't get unexpected type errors.

What is expected to happen?

The UserProfile type matches the actual data coming back from the Okta API.

What is the actual behavior?

The type says that the data cannot be null, but when you access it at runtime, node throws a TypeError and crashes the application.

Reproduction Steps?

• Fetch a user with nulls in the profile data
• In our case "mobilePhone" and "secondEmail" were getting returned as nulls for certain users
• Try to do something on that attribute like trim() that expects the value to be there
• Watch node crash

SDK Versions

"@okta/okta-sdk-nodejs": "6.6.0"

Execution Environment

node --version
v16.19.0

yarn tsc --version
Version 4.9.5

Additional Information?

No response

[denysoblohin-okta]

Thanks for submitting this issue.
Internal ref: OKTA-593025