When should you use ASP identity

Question

0.00/5 (No votes)

See more:

When is it right to use ASP.Net Identity?
When you're Making a single store or single role based app like the Music store, or an Internal Process site?

Should I really be using Identity if I want to add Parent Customers that have more than 1 user? If I want to be adding Discount Codes? A Full Shopping Experience?

How much can you really Customize the user, and how would you link them to Parent Users, how would you allow shipping to multiple address? Or keep a record of them.

What I have tried:

Well I learned Lots about Identity, and Making Roles..
But linking users to Parent Users or Companies doesn't seem to work the way I expected. Multiple Address didn't work as expected too.

Posted 12-Jun-19 15:07pm

juan_van

Updated 17-Jun-19 9:33am

Add a Solution

3 solutions

Solution 2

You can use Identity on simple sites, complex sites, or even a complex family of sites.

The first time I used it was in it's infancy; and it was used in conjunction with the profile and role providers. It was a little overkill as there was only a handful of users.
My current employer has been using this forever; and our last incantation is as an OpenID provider for an enterprise B2B eCommerce application doing > 1 billion USD annually.

The key to success is not only knowing how it works; you also need to know what your needs are and hwo you plan to implement. My first experience was a waste of time as it was overkill for its purpose.

Posted 13-Jun-19 0:14am

MadMyche

Updated 13-Jun-19 0:17am

v2

Solution 3

Took to looking for more answers today, and found this on Microsoft's Best Practices.
[ASP.NET Core application architecture guidance]

This Microsoft Example on Github have 2 DbContext - Many of the projects I found on Gihub and other's have the

C#

ProductDbContext : IdentityDbContext<AppUser...>
DbSet<Order> Orders {get; set;}

Thank's for the Input!

Posted 17-Jun-19 9:33am

juan_van

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)

F-ES Sitecore · Accepted Answer · 2019-06-12T22:14:00

Identity really just handles users, logins, roles, and basic profile info. If you're building something like an ecommerce on top of that, you'll need to implement any additional logic yourself. Users are just rows in a database with a GUID ID so if you want to attach a basket to a user you just have a "UserID" field in your Basket table that contains the ID of the current user. If you want to group users into parents and children then again just create a table that has ParentID and ChildID and manage the data yourself. You can probably extend the user profiles to contain addresses but it's a bad idea. Again just create an Address table that contains the fields you need and store the UserID in that as well.