0
votes

I'm really struggling with these Azure AD concepts.
Here is my situation. I have a webapp with users belonging to Companies. I have a requirement that is to be able to authenticate those users through their Companies' Azure AD. Eventually, We would want to offer this in the Azure app gallery in the future.

I started registering the app through App Registration, which gives me the information to integrate using OIDC. We would like to support both, OIDC and SAML protocols (I see that there are apps in the gallery offering both).

I tested OIDC out and it's working correctly, but when I want to develop SAML integration, the documentation says that it has to be done using an enterprise application. I can't edit the SSO section of the enterprise app generated by my registration:

The single sign-on configuration is not available for this application in the Enterprise applications experience. MY APP was created using the App registrations experience.

so I tested creating a new enterprise app. Using this app I can do all the SAML flow correctly.

My questions here are:

  1. Do I have to connect the registrated app with the enterprise app? How I do that?
  2. Why I can't edit the SSO info in the enterprise generated app?
  3. If it's done through the registration app. Where do I set up the SAML endpoints, certificates etc.?

By reading the docs, I understand that enterprise apps are like "an instance of a registered app". That leads me to think that I should configure all in the registered app, but I can't see how to support SAML.