Handle apps with the "MFA_AS_SERVICE" sign-on mode

[BinoyOza-okta]

Add MFA_AS_SERVICE SignOn Mode Support

Summary

This PR adds support for the MFA_AS_SERVICE application sign-on mode to the Okta SDK for Python. This new authentication mode is now available as an option when listing and working with applications.

Changes Made

Modified Files

1. okta/models/application_sign_on_mode.py

   • Added MFA_AS_SERVICE enum value to ApplicationSignOnMode
   • Updated documentation to include the new sign-on mode

2. okta/models/application.py

   • Added MFA_AS_SERVICE to the discriminator mapping
   • Updated type unions to include Application for MFA_AS_SERVICE mode
   • Added import handling for the new sign-on mode type
   • Added # noqa: F811 to suppress linting warning for self-reference

3. openapi/api.yaml

   • Added MFA_AS_SERVICE to the ApplicationSignOnMode enum
   • Added discriminator mapping for MFA_AS_SERVICE to base Application schema

4. docs/ApplicationSignOnMode.md

   • Updated documentation table to include MFA_AS_SERVICE

Technical Details

The MFA_AS_SERVICE sign-on mode maps to the base Application class (unlike other sign-on modes that have specific subclasses like OpenIdConnectApplication, SamlApplication, etc.). This is handled through:

• Discriminator mapping: "MFA_AS_SERVICE": "Application"
• Self-referencing import in the Application model
• Proper type checking and deserialization support

Testing

• Verified that the new sign-on mode is properly recognized in the list_applications() operation
• Ensured backward compatibility with existing sign-on modes

API Compatibility

This is a backward-compatible change that adds a new option without modifying existing functionality.