1

I want to create a new .NET application with implemented Individual User Accounts. Actually, there is no more possible to create it with users stored in local DB so Active Directory is necessary. I created AD on Azure but have no clue how to fill this form.

enter image description here

I have a problem with all three inputs.

I have 3 question:

  1. How to fill this form?

  2. Is there any reason why I should implement Authentication by myself.

  3. Is there other solution to get authentication out of the box? (like template with already implemented authentication)

Improve this question
1
  • 1
    You're creating a Web API application. Those aren't generally expected to have UI. That's why you're not offered the opportunity to do local logons. I concede that the description does say it can also do MVC in there, the fourth template (Web Application (Model View Controller)) says that it can also be used for restful services (i.e. it's described the opposite way around from the template you've picked) and that template does offer local accounts. Commented Jan 24, 2018 at 15:37

1 Answer 1

Reset to default
1

To answer your first question, filling out the form, you will need to get these details from the Azure AD you setup. The Domain Name is the domain you created in Azure Ad. The Application ID is the guid you got when you registered your application in your Azure AD. The last field, Sign-up or sign-in policy, is the Azure AD policy you want to use to manage people signing up for your service as well as signing into your service.

The problem is, setting up your Azure AD is only one step out of many. What you should be learning how to do is setting up Single Sign On (SSO) using Azure AD. For that, I suggest looking at Authentication Scenarios for Azure AD, What is application access and single sign-on with Azure Active Directory? and Azure Active Directory B2C: Built-in policies. These series of articles should put you on the right path to get started with using Azure AD.

Your second question can be subjective, so I'll simply point things you will need to concern yourself with if you try to implement your own authentication. The biggest problem with doing it your self is making sure you have addressed the necessary security concerns. You will need to have your passwords stored securely which means salting and hashing them (I suggest Googling if you aren't aware of those term). You will also need to handle scenarios like password reset, forgetting user name and/or handling inactive or disabled user accounts. Many organizations and developers like using third party providers for SSO so they don't have to deal with such issues.

For your last question, yes there are. Microsoft does include a basic one with their web project templates (if you choose) and there are other providers out there such as Google or Facebook. There are many other options out there that are open source. A quick search on NuGet yielded over 2k results (https://www.nuget.org/packages?q=user+authentication).

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.