Pramus
Pramus
Explore posts from servers
DTDrizzle TeamKKinde
PostsComments
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
As I see it, Kinde without the custom login flow is not ready for multi-tenancy
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
That would require creating an entire custom login flow, it's not an ideal solution but it is what it is
27 replies
KKinde
Created by ryno1234. on 5/4/2024 in #💻┃support
Automatically adding user to organization on sign-in (not sign-up)
I believe this case and mine are great examples identifying the missing parts of the scenario of an existing user logging into a new organization. It would be great if we could have a setting (per organization possibly?) to determine he behaviour: - inform that they don't have access - as it is now - add to organization - happens in the backgrounds by simply adding the existing user to org and successfully redirects
20 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
Thank you @Oli - Kinde . As a small hint - I believe the behaviour I'd expect is already achievable like @palooka8300 mentioned but only via custom interface using the API. Therefore the change in the out-of-the-box flow (by what I mean your React components and Kinde authentication flow) shouldn't be a big thing. What I can think of could be some kind of an opt-in flag inside organizations to prompt the users existing in the common pool to register anew in the new org instead of alerting them that they don't have permissions. That should give the end users the experience of multi-tenancy.
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
Please refer to the Scenario I described in my original post
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
The user that registered to one tenant (organization), shouldn't be getting a message on another tenant (organization) that they don't have access but rather be asked to register.
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
The issue I described in my original post and the followup comment
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
That would be great but I'm not sure we are on the same page - what I mean is that even with the common user pool there is an issue
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
Ok but the problem described in my post persists...
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
Like I mentioned - I'm building a multi-tenant application. The experience I want to achieve is described in the post. Each instance should be completely independent. Therefore I'd like to allow uses to have 'separate' accounts per tenant. There are two solutions though: 1. Consequently separate user pools - organizations don't allow that since the users are in one pool anyway. I'm not sure if it's achievable with Kinde. 2. A compromise - use one pool but assign users to the tenant organization on registration. It'd be ok for me (as I have my own users table per tenant db and can hold additional data there) if not for the problem described in the post.
27 replies
KKinde
Created by ryno1234. on 5/4/2024 in #💻┃support
Automatically adding user to organization on sign-in (not sign-up)
I have a similar problem: https://discord.com/channels/1070212618549219328/1233335354023743541
20 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
@Claire_Kinde I'm afraid that this thread went down the list. Do you know anyone who could answer this question?
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
I'm afraid that the docs you provided don't cover that scenario but thank you anyway 🙂
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
Right. I'll bump it on Monday then. Good call, thanks!
27 replies
KKinde
Created by Pramus on 4/26/2024 in #💻┃support
Separate login per organization
I'm using <LoginLink /> and <RegisterLink /> components in NextJS provided by Kinde. Indeed the issue probably might be solved using custom UI but I believe there's room for improvement for Kinde auth pages as well. I swap the "orgCode" property depending on the instance and that's how I noticed that behavior.
27 replies
DTDrizzle Team
Created by Pramus on 4/23/2024 in #help
SQLean's uuid4() in SQLite CREATE TABLE
I think I might've figured out what is the problem. Not sure if it exists in code but definitely in Drizzle Studio. I created an issue on GitHub: https://github.com/drizzle-team/drizzle-orm/issues/2198
7 replies
DTDrizzle Team
Created by Pramus on 4/23/2024 in #help
SQLean's uuid4() in SQLite CREATE TABLE
No description
7 replies
DTDrizzle Team
Created by Pramus on 4/23/2024 in #help
SQLean's uuid4() in SQLite CREATE TABLE
Unfortunately this results in a broken syntax (note I mistakenly removed one DEFAULT from my initial output, fixed it): 
    `id` text PRIMARY KEY DEFAULT DEFAULT(uuid4()) NOT NULL,
    `id` text PRIMARY KEY DEFAULT DEFAULT(uuid4()) NOT NULL,
AFAIK the syntax for default values is DEFAULT + value rather than DEFAULT(value)
7 replies
DTDrizzle Team
Created by Pramus on 4/5/2024 in #help
libSQL/SQLite: Issue with CAST and ILIKE
Forget it... libSQL/SQLite doesn't have ILIKE, my bad. I'll leave it here just in case someone does the same mistake. Here's the correct code: 
      .where(
        or(
          sql`LOWER(customers.name) LIKE ${`%${query.toLowerCase()}%`}`,
          sql`LOWER(customers.email) LIKE ${`%${query.toLowerCase()}%`}`,
          sql`CAST(LOWER(invoices.amount) AS TEXT) LIKE ${`%${query.toLowerCase()}%`}`,
          sql`CAST(LOWER(invoices.date) AS TEXT) LIKE ${`%${query.toLowerCase()}%`}`,
          sql`LOWER(invoices.status) LIKE ${`%${query.toLowerCase()}%`}`,
        ),
      .where(
        or(
          sql`LOWER(customers.name) LIKE ${`%${query.toLowerCase()}%`}`,
          sql`LOWER(customers.email) LIKE ${`%${query.toLowerCase()}%`}`,
          sql`CAST(LOWER(invoices.amount) AS TEXT) LIKE ${`%${query.toLowerCase()}%`}`,
          sql`CAST(LOWER(invoices.date) AS TEXT) LIKE ${`%${query.toLowerCase()}%`}`,
          sql`LOWER(invoices.status) LIKE ${`%${query.toLowerCase()}%`}`,
        ),
2 replies