Azure-docs: Sap Netweaver metadata xml no longer accepted

[dverbiest1]

[Enter feedback here]
recently the upload of metadata xml fails for SAP Netweaver. The error is The Blade extension/Microsoft_AAD_IAM/Blade/SamlBlade failed to supply all the required parameters. The missing the required parameter(s): 'signOnUrl'

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ccaf7a87-3d5a-521e-5fd3-39967ba6a233
• Version Independent ID: e2bca7c3-f330-8e1f-518e-cc17415f0338
• Content: Tutorial: Tutorial: Azure Active Directory Single sign-on (SSO) integration with SAP NetWeaver
• Content Source: articles/active-directory/saas-apps/sap-netweaver-tutorial.md
• Service: active-directory
• Sub-service: saas-app-tutorial
• GitHub Login: @jeevansd
• Microsoft Alias: jeedes

[SaurabhSharma-MSFT]

@dverbiest1 Thanks for the feedback ! I have assigned this issue to content author to investigate and update the document as appropriate.

[Taaqif]

Experiencing the same issue with a different identity provider

[tvdijen]

The issue is that 'SignOnUrl' is not part of the SPSSODescriptor in SAML 2.0 metadata.. Therefore it cannot be a mandatory field when importing metadata. If MS requires it somehow, they should define a metadata-extension

[jeevansd]

@tvdijen This is a bug in the portal right now. The fix is getting deployed and it should be live by end of this week.

[jeevansd]

@Taaqif Please see my comment above.

[tvdijen]

Great, thanks!

There is actually a metadata extension defined that does exactly what you guys want for the SignOnURL.. http://docs.oasis-open.org/security/saml/Post2.0/sstc-request-initiation-cs-01.pdf
If, for convenience, you want to support importing this setting from the metadata XML, you may want to consider using this extension

[jeevansd]

@tvdijen I know but they are optional per the specification. Right now the portal is expecting this as mandatory, so we are removing that check.

[xaviertop]

@jeevansd have you an idea when you deliver a new release without this error ? it block some process in our company to create azure application with SAML authentification.
thanks

[tvdijen]

@xaviertop What's holding you back from manually entering the settings instead of the XML upload?

[xaviertop]

@tvdijen yes i can add this manually but i have a workflow which create azure application automatically and set saml configuration on it

[criscunhasantos]

AWS SSO federation metadata not accepted as well:
The blade Extension/Microsoft_AAD_IAM/Blade/SamlBlade failed to supply all the required parameters. The missing the required parameter(s) 'signOnUrl, logoutUrl'.

[jeevansd]

Yes, this is known issue for multiple applications now. As I have said before the fix is already in the deployment.

[adin3d]

@jeevansd any update on this - it is a really big problem? Already in deployment means that it should work now?

[jeevansd]

This issue is resolved now. You can verify this in the portal also.

[jeevansd]

please-close