Skip to content

Conversation

@OscarMoya
Copy link

WIP work for the authentication service compatible with OAuth

@OscarMoya OscarMoya marked this pull request as draft June 13, 2024 07:33
__tablename__ = "users"

id = Column(Integer, primary_key=True, index=True)
tenant_id = Column(Integer, index=True) # Not sure about this one
Copy link
Member

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.

Copy link
Author

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

__tablename__ = "users"

id = Column(Integer, primary_key=True, index=True)
tenant_id = Column(Integer, index=True) # Not sure about this one
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Humm.. Name?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And username

Copy link
Author

@OscarMoya OscarMoya Jun 14, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants