Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

decouple Account class from EF Core Identity #599

Open
bacongobbler opened this issue Apr 5, 2022 · 0 comments
Open

decouple Account class from EF Core Identity #599

bacongobbler opened this issue Apr 5, 2022 · 0 comments
Labels
refactor Identifies code that needs to be refactored

Comments

@bacongobbler
Copy link
Contributor

bacongobbler commented Apr 5, 2022

Because a few of the core objects inside Hippo rely on account information, we should de-couple the EF Core identity framework from the Account we store in the database, using a common ID like a user ID, email address, or username to link the two identities.

This will make it much simpler to separate the application's concerns from the identity.

@bacongobbler bacongobbler added the refactor Identifies code that needs to be refactored label Apr 5, 2022
@bacongobbler bacongobbler modified the milestones: v0.6.0, v0.7.0, API Security Apr 5, 2022
@bacongobbler bacongobbler removed this from the API security milestone May 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
refactor Identifies code that needs to be refactored
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant