I have a stand alone application that I want to add as an Identity Provider (IdP) in Azure AD.
The idea is that internal users can login with their normal on-prem AD credentials, and external users will login with the credential provided by this custom IdP.
Does anyone have experience with this?
I'm using ComponentSpace to add the SAML2 capabilities but I'm struggling with the deprecated and contradictory information on the web.
I believe we're still on a limbo stage when it comes to AD on Azure.
ACS is supposed to be replaced by B2C but both still exist and the custom IdP functionality haven't been ported yet.
Trying to configure Azure AD also still redirects me to the old portal which reinforces my "limbo" theory.
I knew those references already, I was more looking for someone who had actually done it and get some field feedback from that experience.
ComponentSpace simply says (and well) that they handle the SAML part, whoever needs to consume it it's not their business :)
I'll close this question now.
I'll mark your answer as accepted just because the last link is in fact what it's needed to federate a custom SAML2 IdP.
Cheers!
.NET Programming
The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.
ASKER
I believe we're still on a limbo stage when it comes to AD on Azure.
ACS is supposed to be replaced by B2C but both still exist and the custom IdP functionality haven't been ported yet.
Trying to configure Azure AD also still redirects me to the old portal which reinforces my "limbo" theory.
I knew those references already, I was more looking for someone who had actually done it and get some field feedback from that experience.
ComponentSpace simply says (and well) that they handle the SAML part, whoever needs to consume it it's not their business :)
I'll close this question now.
I'll mark your answer as accepted just because the last link is in fact what it's needed to federate a custom SAML2 IdP.
Cheers!