How to implement authentication for web services?

Question

ASP.NET

Now we are building a corporate portal with the following SOA architecture:
Web forms on ASP.net MVC are the point of interaction with web services that represent their logic.
- Web services can be either self-written WCF applications on IIS, or third-party software interfaces
- identification must occur through Active Directory.
-It is supposed to use a role-based authentication model on services and forms.
identification, presumably takes place on the portal. In the same place, the interface is adjusted to the user's role
Tell me how to organize identification and authentication according to this scheme?
Dug in the direction of SSO, SAML, FIM, ADFS, etc., but has not yet decided on the answer.
For me, now the scheme looks like this - build an iDp provider that distributes tokens via SAML, then slowly clean up AD and rebuild it to meet new requirements.
Doesn't anyone have similar experience?

Answer 1

Choose SAML. Not a bicycle and not a collective farm, but an enterprise standard. You can use ready-made solutions, there are both paid and free ones.
We work with PingFederate, Satisfied.