Layers in Clean Architecture Asp.net Core 5

Mahdi Elahi 26

Hi,
this my layers in clean architecture , see the photo

1.Is this clean architecture observed?
2. i want add identity to project , Which layer should I add identity (authentication) to?

AgaveJoe 26,136 Reputation points

2021-11-27T17:26:31.107+00:00

1.Is this clean architecture observed?

You shared projects in folder but not there's not enough information to determine if logic within the project follows "clean architecture".

i want add identity to project , Which layer should I add identity (authentication) to?

Most likely the data access layer. But, it depends on how many physical tiers exist in the application which is unknown at this time. If you have one host, one database server, and vanilla Identity then just implement the Identity library (RCL).
Mahdi Elahi 26 Reputation points

2021-11-28T17:07:47.607+00:00

i add and use identity (usermanager / signInmanager / roleManage) in userService.cs in DataLayer

i define my user services in data layer and use services in my webclient

please check if use identity in clean architecture its true or not ?

this my project userManagement
Mahdi Elahi 26 Reputation points

2021-12-01T15:48:18.563+00:00

i add and use identity (usermanager / signInmanager / roleManage) in userService.cs in DataLayer

i define my user services in data layer and use services in my webclient

please check if use identity in clean architecture its true or not ?

this my project userManagement

please help us to this problem

2 answers

Bruce Barker 801 Reputation points

2021-11-27T20:15:35.337+00:00

There should be multiple layers for identity. The actual ui will be in the UI layer, but you will have adapters to convert to poco entities that can be passed to business rule layer, which will implement the access rules.
Please sign in to rate this answer.
Mahdi Elahi 26 Reputation points

2021-11-28T17:09:29.483+00:00

i use identity in data layer and user service and use these services in webclient , its true ?

this my project userManagement
Sign in to comment
Bruce (SqlWork.com) 56,771 Reputation points

2021-11-30T17:32:30.873+00:00
you appear to be using DI with repository pattern, this is slightly different than clean. in clean,

entity (domain) layer: poco objects with with localized validation rules (formatting etc)
use cases (business) layer: business logic that performs actions on entities
controllers layer: adapters to access services like a database databases,
external layer: ui, rest api, etc

the logic for a use case is:

map request data to entity

call adapters get an external data

call use case logic

map use case response to external data

an external layer action may require multiple use cases. for example update name in a user record:

validate access

map request to security request

call adapter to get user record security object

call business rule to valid access

do name change

map request to name change object

call adapter to read user entity

call business rule apply name change to user entity

call adapter to save user entity

return result

map to response
Please sign in to rate this answer.
Mahdi Elahi 26 Reputation points

2021-12-01T15:47:11.497+00:00

please show me a clean architecture project with use identity authorization in .net core

Bruce (SqlWork.com) 56,771 Reputation points

2021-12-01T16:30:26.533+00:00

Clean architecture is a coding style designed for TDD. All logic for accessing external resources (database, web services, etc) are moved to adapters that return POCO entity objects. all business logic should only use entities. so the pattern is:

call adapters to get entities
call business logic with entities
call adapters to save entities

identity is typically two operations

1) authentication (who the user is), typically done in the UI layer
2) authorization (what the user is allowed to do)

typically authentication would return user object with claims (or roles depending on your authorization model). to support any authentication scheme, you would use an adapter to convert the native user & claims to entities that the business rules understand.

authorization would be performed by the business rules for each use case.

note: Clean is about the design and less about the project structure. a good starting point would be to create four projects:

1) a .net web UI project
2) an entities project (no project references)
3) the business rules project (only references entities)
4) an adapters project (only references entities)

this will keep you from leaking functionality between layers.
Sign in to comment