You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: handle nullable discriminator fields in JWKS models (#514)
* fix: handle nullable discriminator fields in JWKS models
Fixes deserialization failures when Okta API returns null values for
discriminator fields in JWKS (JSON Web Key) responses.
Changes:
- Updated OpenAPI spec to mark JWKS fields as nullable (created, lastUpdated, kty, alg, use, e, n)
- Updated documentation to reflect nullable fields
All changes are template-based to survive SDK regeneration.
Resolves customer-reported issues where list_applications() failed with
"ValueError: Failed to lookup data type from the field `use`" when JWKS
keys contained null values.
* fix: add missing JWKS subclass fields to serialization
- Added e, n fields to OAuth2ClientJsonWebKeyRsaResponse __properties and from_dict()
- Added x, y, crv fields to OAuth2ClientJsonWebKeyECResponse __properties and from_dict()
- Marked crv as optional (nullable) per API specification (x, y remain required)
- Added null preservation for e, n, crv in to_dict() methods
This ensures RSA and EC JWKS keys properly serialize/deserialize all subclass-specific fields.
* - Reverted the change of making kty as optional.
0 commit comments