Skip to content

fix: return raw application JSON from get_application so attribute statements are readable - #71

Open
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:fix/get-application-raw-readback
Open

fix: return raw application JSON from get_application so attribute statements are readable#71
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:fix/get-application-raw-readback

Conversation

@mjdavidson

Copy link
Copy Markdown

get_application returned the typed SDK model, which the MCP layer serializes with pydantic model_dump — rendering SAML attributeStatements as opaque anyOf union stubs (no name/values), and raising on apps with a sparse settings.signOn. Returns Okta's JSON verbatim via the request executor, matching the approach used by list_applications.\n\nTests: tests/test_get_application.py.

…atements are readable

get_application returned the typed SDK model, which the MCP layer serializes
with pydantic model_dump. For SAML apps that renders
settings.signOn.attributeStatements as opaque anyOf union wrappers
(actual_instance / any_of_schemas) rather than their real type/name/namespace/
values, so a caller can't read back which attributes are configured even though
they work at sign-on. The typed deserialization also raises on apps whose
settings.signOn omits fields the SDK marks required.

Fetch the application through the request executor and return Okta's JSON
verbatim, matching the approach already used by list_applications. Attribute
statements now read back with their real fields, and sparse apps no longer
break the call.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant