[CAL-3837] Credential.Key error when booking

[sabzo]

Found a bug? Please fill out the sections below. 👍

Issue Summary

Users can't book meetings

Steps to Reproduce

Actual Results

Expected Results

• a successful booking

Technical details

• happens on chrome, safari, brave on mobile, iPad and desktop

Evidence

• tested on multiple devices as described above

_{From SyncLinear.com | CAL-3837}

[dosubot]

Hey @sabzo! 👋 I'm here to help you with any bugs, questions, or contributions you might have regarding the repository. Let's squash those bugs together!

To resolve the "Credential.Key error" that prevents users from booking meetings, ensure that all required fields in the albyCredentialKeysSchema are correctly provided and validated. The required fields are:

• account_id
• account_email
• account_lightning_address
• webhook_endpoint_id
• webhook_endpoint_secret

Here is the schema for reference:

import z from "zod";

export const albyCredentialKeysSchema = z.object({
  account_id: z.string(),
  account_email: z.string(),
  account_lightning_address: z.string(),
  webhook_endpoint_id: z.string(),
  webhook_endpoint_secret: z.string(),
});

Additionally, ensure that the user ID and credential ID are valid numbers, as these are also critical for the credential validation process. The following schema definitions from the apps/api/v1/lib/validations/credential-sync.ts file can help ensure proper validation:

import { z } from "zod";
import { HttpError } from "@calcom/lib/http-error";

const userId = z.string().transform((val) => {
  const userIdInt = parseInt(val);
  if (isNaN(userIdInt)) {
    throw new HttpError({ message: "userId is not a valid number", statusCode: 400 });
  }
  return userIdInt;
});

const credentialId = z.string().transform((val) => {
  const credentialIdInt = parseInt(val);
  if (isNaN(credentialIdInt)) {
    throw new HttpError({ message: "credentialId is not a valid number", statusCode: 400 });
  }
  return credentialIdInt;
});

export const schemaCredentialGetParams = z.object({
  userId,
  appSlug: z.string().optional(),
});

export const schemaCredentialPostParams = z.object({
  userId,
  createSelectedCalendar: z.string().optional().transform((val) => val === "true"),
  createDestinationCalendar: z.string().optional().transform((val) => val === "true"),
});

export const schemaCredentialPostBody = z.object({
  appSlug: z.string(),
  encryptedKey: z.string(),
});

export const schemaCredentialPatchParams = z.object({
  userId,
  credentialId,
});

export const schemaCredentialPatchBody = z.object({
  encryptedKey: z.string(),
});

export const schemaCredentialDeleteParams = z.object({
  userId,
  credentialId,
});

For Office 365 calendar integration, ensure that the client_id and client_secret are correctly provided and validated using the officeAppKeysSchema:

import { z } from "zod";

import getParsedAppKeysFromSlug from "../../_utils/getParsedAppKeysFromSlug";

const officeAppKeysSchema = z.object({
  client_id: z.string(),
  client_secret: z.string(),
});

export const getOfficeAppKeys = async () => {
  return getParsedAppKeysFromSlug("office365-calendar", officeAppKeysSchema);
};

Make sure that the credentials provided to the application match these schemas to avoid the "Credential.Key error" ^[1][2][3].

To continue talking to Dosu, mention @dosu.