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
This commit introduces a post-processing mechanism to handle Application
objects with signOnMode values that are not defined in the ApplicationSignOnMode
enum, preventing deserialization errors when new sign-on modes are introduced
by Okta.
Changes:
- Added post_process_application.py script with custom deserialization logic
- Implements x-post-process-function vendor extension support
- Updated api.yaml to reference post-processing for Application schema
- Modified model_generic.mustache to invoke post-processing when defined
- Added OTHER enum value to ApplicationSignOnMode for unknown modes
The solution uses OpenAPI Generator's vendor extension mechanism (x-post-process-function)
to apply custom deserialization logic specifically to the Application model without
affecting other models in the SDK.
When an Application response contains an unknown signOnMode:
1. Discriminator resolution falls back to 'OTHER' mapping
2. Post-processing preserves the original signOnMode value
3. Application object is returned with the actual value from API response
4. SDK remains forward-compatible with new Okta sign-on modes
This prevents breaking changes when Okta introduces new application types
like MFA_AS_SERVICE while maintaining type safety for known values.
Fixes: Deserialization errors for applications with unknown signOnMode values
0 commit comments