AdamM.90568 (Customer) asked a question.
/api/v1/apps/{appId}/sso/saml/metadata endpoint responding with 404
Hello,
I currently work with Okta API and encountered a problem with /api/v1/apps/{appId}/sso/saml/metadata endpoint as it is, for some apps, responding with 404. I noticed that it responds with 404 only for the inactive apps and with 200 for active apps (and also always with 200 for Okta-type apps like Okta Admin Console).
The question is: is that a rule that the mentioned endpoint responds with 404 only for inactive apps? And it is just not documented in the API documentation (https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSO/)? Or maybe it is documented somewhere but I just missed it?
Thanks in advance!
I'm not finding any documentation either on this topic but why would you want SAML metadata for an inactive app? I would not think the endpoints described in the metadata would be accessible so I would see no reason for inactive app SAML metadata to be returned by API. Perhaps you could share info about your specific use case as it might help others provide better answers.