4bmaj (4bmaj) asked a question.
Bug in the Developer Console UI
We have an okta preview environment where I manage two internal apps (that we use for testing integrations). I was setting up SAML integration and noticed that the section to download Identity provider metadata link does not appear in the new Developer Console UI view. If I switch to the `Classic UI` view, the section appears.
I am referring to Step no. 7 in this support article - https://support.okta.com/help/s/article/How-do-we-download-the-IDP-XML-metadata-file-from-a-SAML-Template-App
Hi Guru,
Thank you for reaching out to Okta Support!
When you're using the Developer console on your Okta developer org, the UI is designed for developers to integrate/create OIDC apps,Single-Page apps (Angular,React etc.) and other services, it is not designed for SAML,WS-fed,SWA apps.
You can verify this behavior by going to Applications using the Developer Console, when you click on Add Application, you'll be able to create only OIDC,Single-page APps,Web (.net,Java etc) and other services.
You will still be able to access the already configured SAML apps using the developer console but with limited view of resources, as stated in your comment, the IDP Metadata download button.
By switching to the Classic UI, you'll be able to configure SAML IDP's,SP's etc. , providing developers the ability to switch between consoles for easier access to our resources.
This indeed is expected behavior found on any Okta developer instance.
If you'll have any questions or require assistance, please open a case with Okta Support.
I see, thanks for letting me know!