-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft: Authentication Service Model and Views #3
base: main
Are you sure you want to change the base?
Conversation
src/models/authentication.py
Outdated
__tablename__ = "users" | ||
|
||
id = Column(Integer, primary_key=True, index=True) | ||
tenant_id = Column(Integer, index=True) # Not sure about this one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see DH being multi-tenant anytime soon. I would see RBAC fit the bill for most of the things, so I would add Roles"
Having said that, leave it. JIC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I will make it nullable and optional so it does not slowdown the implementation
src/models/authentication.py
Outdated
__tablename__ = "users" | ||
|
||
id = Column(Integer, primary_key=True, index=True) | ||
tenant_id = Column(Integer, index=True) # Not sure about this one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Humm.. Name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And username
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, bear in mind that there are some providers (oAuth) that they don't have any name, just the email . This is OK as emails are unique and you don't need additional unique constrains on the DB. That being said, if you want we can do it optional and if not provided use the email as user-name
WIP work for the authentication service compatible with OAuth