Click here to Skip to main content
14,030,875 members
Rate this:
Please Sign up or sign in to vote.
See more: , +

I'm planning to write a few api's to improve my programming knowledge. But as a starter I'm thinking about authentication. I've been searching for a solution, but I'm wondering if there are better options. What I want to achieve is to have a AuthenticationAPI which handles the authentication. I want to have a kind of a microservice architecture with a few small app's/api's. The authentication (and authorisation) should be handled by the AuthenticationAPI.

What I have tried:

While searching for a solution, I ended up with IdentityServer. Which can generate a token, which can be "shared" across other app's/api's. Each app/api can check with the AuthenticationAPI if the token is still valid.

But I'm wondering if there are better options for such a architecture? Could anyone provide some other options? That would be highly appreciated.
Updated 6-Jan-19 22:57pm
Nathan Minier 29-Sep-17 7:50am
I live in an MS world, so we just use AD and Kerberos. If you have a backend infrastructure, LDAP is a well-supported and inter-operable mechanism for managing AAA actions that supports SSO.

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 1

IdentityService is the best solution so far I know because it allows you to make service to service authentication and service to consumer authenitcation. I have used it in serveral projects successfully and got a good results.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy | Cookies | Terms of Service
Web05 | 2.8.190419.4 | Last Updated 7 Jan 2019
Copyright © CodeProject, 1999-2019
All Rights Reserved.
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100