How to implement basic authentication in web api

Question

0.00/5 (No votes)

See more:

Hi all,

I know its a very basic question but i got confuse after google it because people implemented in different ways. so my major concern is what's standard way to implement basic authentication in api.

I go through following links:

What I have tried:

Token Based Authentication using ASP.NET Web API 2, Owin, and Identity - Bit of Technology[^]

ASP.NET Identity 2.1 Roles Based Authorization with ASP.NET Web API - Part 4 - Bit of Technology[^]

Basic Authentication in Web API Based on User Role[^]

Posted 7-Nov-16 19:27pm

Member 8233601

Updated 7-Nov-16 20:51pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

M.Kamran Asim · Accepted Answer · 2016-11-07T20:51:00

Hello,

It depends on purpose of your web Api. For example if you exposing Api to public just like Google Adwords and Yahoo Gemini also you dont want to use username/password for each protected resource. Go for Token based authentication.
For general purpose I will suggest you to use Token based.

Quote:
The general concept behind a token-based authentication system is simple. Allow users to enter their username and password in order to obtain a token which allows them to fetch a specific resource - without using their username and password. Once their token has been obtained, the user can offer the token - which offers access to a specific resource for a time period - to the remote site.

Asp.Net Identity is best suited for Organizational Api like Financial applications, Human resource and services. You can protect your API based on Roles and authentication. On each request you have to authenticate your self by username/password etc.
Asp.Net Identity provide you huge verity and support OAuth integration, works with OWIN.