Client Identity x Azure AD x ADFS integration

Asked

Viewed 67 times

-1

I have a database authentication application using OWIN and Identity. A client requested single Sign on with ADFS on premisse. I did it directly through OWIN, but the client requests a federation url (with metadata), which I don’t have. To circumvent, I think to authenticate with Azure AD with the least effort possible (I thought to use the ldap library and only check if the user exists) and in Azure AD configure the SSO.

This scenario is valid?

asp.net asp.net-identity active-directory owin

1 answer

0

Identityserver will be your best way out. It will provide you with all possible and necessary means of accreditation.

It supports multiple ways of authentication:

  • Windows Integrated Authentication: if you are running on a Windows Server with IIS and within an AD domain.
  • Username/password: via LDAP and federation (with Openid Connect/ADFS or domain next to Identityserver)

And with it you create SSO (Single Sign On) for as many applications as you need, using user level or level accreditation app client.

Browser other questions tagged asp.net asp.net-identity active-directory owin

You are not signed in. Login or sign up in order to post.