Jacob
Jacob
Explore posts from servers
CDCloudflare DevelopersBABetter Auth
PostsComments
BABetter Auth
Created by Acro on 4/6/2025 in #help
Clarification on Email OTP Auth Flows
Just do sign in with OTP. You dont need passwords or email verification since they get the OTP in their inbox. I do a combined sign in / sign up on same form.
3 replies
BABetter Auth
Created by MaveriX89 on 3/12/2025 in #help
Adding Members to Organization with Teams Enabled
https://github.com/better-auth/better-auth/issues/2002
18 replies
BABetter Auth
Created by Jacob on 3/23/2025 in #bug-reports
The field "teamId" does not exist in the "invitation" schema.
Also needs update on member table for teamId
3 replies
BABetter Auth
Created by MaveriX89 on 3/12/2025 in #help
Adding Members to Organization with Teams Enabled
We also need an update member to apply a new team. I think it’s only update role.
18 replies
BABetter Auth
Created by MaveriX89 on 3/12/2025 in #help
Adding Members to Organization with Teams Enabled
I would love to see support for multiple teams with another schema table. I just added a request to update the docs for missing team id in the invitation table so I will add the member table update there.
18 replies
BABetter Auth
Created by Vimes on 3/18/2025 in #help
Set active org on login
Im using a combo: 
  const activeMember = await auth.api.getActiveMember({
    headers: await headers(),
  });

  const activeOrg = await auth.api.getFullOrganization({
    headers: await headers(),
  });
  const activeMember = await auth.api.getActiveMember({
    headers: await headers(),
  });

  const activeOrg = await auth.api.getFullOrganization({
    headers: await headers(),
  });
That lets you get the users active org and additional details of the org like the name. If active org has been set in session then you don't need to pass the org id.
6 replies
BABetter Auth
Created by Vimes on 3/18/2025 in #help
Set active org on login
You need to use the databaseHooks / user / create / after - then do a direct DB call to make the 1st organization. I use const orgId = nanoid(25); which I assume is close to what better-auth uses. Then when the user logs in the session / create / before will pull in your active org. the function they show getActiveOrganization is something you will have to make yourself. 
async function getActiveOrganization(userId: string) {
  const userMember = await db.query.member.findFirst({
    where: and(eq(memberTable.userId, userId), eq(memberTable.role, "owner")),
    with: {
      organization: true,
    },
  });

  if (!userMember?.organization) {
    throw new Error("No active organization found");
  }

  return userMember.organization;
}
async function getActiveOrganization(userId: string) {
  const userMember = await db.query.member.findFirst({
    where: and(eq(memberTable.userId, userId), eq(memberTable.role, "owner")),
    with: {
      organization: true,
    },
  });

  if (!userMember?.organization) {
    throw new Error("No active organization found");
  }

  return userMember.organization;
}
And org create 
            const orgId = nanoid(25);

            await dbTransaction.transaction(async (tx) => {
              // Create organization
              const [newOrg] = await tx
                .insert(organizationTable)
                .values({
                  id: orgId,
                  name: firstName
                    ? `${firstName}'s Organization`
                    : "My Organization",
                  slug: orgId,
                })
                .returning();

              if (!newOrg) {
                throw new Error("Failed to create organization");
              }

              // Set this as the active organization in the session
              await tx
                .update(sessionTable)
                .set({ activeOrganizationId: newOrg.id })
                .where(eq(sessionTable.userId, user.id));
            const orgId = nanoid(25);

            await dbTransaction.transaction(async (tx) => {
              // Create organization
              const [newOrg] = await tx
                .insert(organizationTable)
                .values({
                  id: orgId,
                  name: firstName
                    ? `${firstName}'s Organization`
                    : "My Organization",
                  slug: orgId,
                })
                .returning();

              if (!newOrg) {
                throw new Error("Failed to create organization");
              }

              // Set this as the active organization in the session
              await tx
                .update(sessionTable)
                .set({ activeOrganizationId: newOrg.id })
                .where(eq(sessionTable.userId, user.id));
6 replies
BABetter Auth
Created by Jacob on 3/23/2025 in #help
Organization inviteMember - Not Allowed to Invite
Ok the solution is that you have to very carefully read the docs and not vibe code, lol. You have to use the default statements or the invitations feature will not work. So for example: 
const statement = {
  ...defaultStatements,
  billing: ["manage_billing"],
  license: ["manage_licenses"],
  app: [
    "view",
    "connect_integration",
    "disconnect_integration",
    "configure",
    "manage_app_permissions",
  ],
} as const;

const ac = createAccessControl(statement);

// Organization owner - has full access to everything
const owner = ac.newRole({
  billing: ["manage_billing"],
  license: ["manage_licenses"],
  app: [
    "view",
    "connect_integration",
    "disconnect_integration",
    "configure",
    "manage_app_permissions",
  ],
  ...adminAc.statements,
});
const statement = {
  ...defaultStatements,
  billing: ["manage_billing"],
  license: ["manage_licenses"],
  app: [
    "view",
    "connect_integration",
    "disconnect_integration",
    "configure",
    "manage_app_permissions",
  ],
} as const;

const ac = createAccessControl(statement);

// Organization owner - has full access to everything
const owner = ac.newRole({
  billing: ["manage_billing"],
  license: ["manage_licenses"],
  app: [
    "view",
    "connect_integration",
    "disconnect_integration",
    "configure",
    "manage_app_permissions",
  ],
  ...adminAc.statements,
});
I didn't read the "invitation" create/cancel and because I didn't inherit the defaults my owner of the organization didn't have those abilities. What was throwing me off is that I was able to update my organizations name even though I did this silly override so that means that even if you screw up you can still as owner update the org. Lesson learned is to actually use the docs examples. 😄
4 replies
BABetter Auth
Created by MeesaWorldWide on 3/23/2025 in #help
pass discord ID to session
Ok my code for mapping it: 
      mapProfileToUser: (profile) => {
        if (!profile.verified) {
          throw new Error("Discord email is not verified.");
        }

        return {
          ...profile,
          discordUsername: profile.username,
          image: profile.avatar
            ? `https://cdn.discordapp.com/avatars/${profile.id}/${profile.avatar}.png`
            : undefined,
        };
      },
      mapProfileToUser: (profile) => {
        if (!profile.verified) {
          throw new Error("Discord email is not verified.");
        }

        return {
          ...profile,
          discordUsername: profile.username,
          image: profile.avatar
            ? `https://cdn.discordapp.com/avatars/${profile.id}/${profile.avatar}.png`
            : undefined,
        };
      },
And there is example code for the organizations plugin that shows how to pass data in the session before its created so use that sample: 
  databaseHooks: {
    session: {
      create: {
        before: async (session: { userId: string }) => {
          try {
            const organization = await getActiveOrganization(session.userId);
            return {
              data: {
                ...session,
                activeOrganizationId: organization.id,
              },
            };
          } catch (error) {
            console.error("Error getting active organization:", error);
            return { data: session };
          }
        },
      },
    },
  databaseHooks: {
    session: {
      create: {
        before: async (session: { userId: string }) => {
          try {
            const organization = await getActiveOrganization(session.userId);
            return {
              data: {
                ...session,
                activeOrganizationId: organization.id,
              },
            };
          } catch (error) {
            console.error("Error getting active organization:", error);
            return { data: session };
          }
        },
      },
    },
But I am interested to see how others would do this.
5 replies
CDCloudflare Developers
Created by Jacob on 2/13/2025 in #workers-help
Worker KV Not Binding
Thx. Should only one or the other exist in the project?
11 replies
CDCloudflare Developers
Created by Jacob on 2/13/2025 in #workers-help
Worker KV Not Binding
Ok made a discovery. So the TOML file still allows a build to go through even if something is wrong/failing and zero log issues. So I started updating the wrangler.jsonc file in addition and finally got some failure logs to discover that I had a wrong KV id number somehow. So whats the point of having a TOML and a jsonc file when they are essentially identical? Should builds only have the jsonc when deploying via github?
11 replies
CDCloudflare Developers
Created by Jacob on 2/13/2025 in #workers-help
Worker KV Not Binding
@Chaika So i made that update so it compiles TOML to JSON properly but it still didn't bind any of the namespaces: 
account_id = "123"
compatibility_date = "2024-11-11"
compatibility_flags = [
    "nodejs_compat",
    "nodejs_compat_v2",
]
main = "./index.js"
name = "auth"
workers_dev = true

[observability.logs]
enabled = true

[[kv_namespaces]]
binding = "CURATED_EMAIL"
id = "abc"
preview_id = "abc"

[[kv_namespaces]]
binding = "CURATED_EMAIL_UNKNOWN"
id = "abc"
preview_id = "abc"

[[kv_namespaces]]
binding = "CURATED_INACTIVE_RETRIES"
id = "abc"
preview_id = "abc"

[[kv_namespaces]]
binding = "CURATED_MULTIPLE_INSTALL"
id = "abc"
preview_id = "abc"

[[kv_namespaces]]
binding = "CURATED_COMPANY"
id = "abc"
preview_id = "abc"

[tail_consumers]
service = "tail"
account_id = "123"
compatibility_date = "2024-11-11"
compatibility_flags = [
    "nodejs_compat",
    "nodejs_compat_v2",
]
main = "./index.js"
name = "auth"
workers_dev = true

[observability.logs]
enabled = true

[[kv_namespaces]]
binding = "CURATED_EMAIL"
id = "abc"
preview_id = "abc"

[[kv_namespaces]]
binding = "CURATED_EMAIL_UNKNOWN"
id = "abc"
preview_id = "abc"

[[kv_namespaces]]
binding = "CURATED_INACTIVE_RETRIES"
id = "abc"
preview_id = "abc"

[[kv_namespaces]]
binding = "CURATED_MULTIPLE_INSTALL"
id = "abc"
preview_id = "abc"

[[kv_namespaces]]
binding = "CURATED_COMPANY"
id = "abc"
preview_id = "abc"

[tail_consumers]
service = "tail"
11 replies
CDCloudflare Developers
Created by Jacob on 2/13/2025 in #workers-help
Worker KV Not Binding
ok this is helpful!
11 replies
CDCloudflare Developers
Created by Jacob on 2/13/2025 in #workers-help
Worker KV Not Binding
Case ID: 01388357
11 replies
CDCloudflare Developers
Created by Jacob on 2/13/2025 in #workers-help
Worker KV Not Binding
No description
11 replies