Hi Kinde Support,
I'm facing an issue with account linking in my app. Currently, a user can create two separate accounts when signing up with passwordless email and Apple Auth.
Is there a way to automatically link these accounts by default if they use the same email address? If not, what would be the best approach to handle this scenario?
Hello, I'm looking to customise the business/application name sent in emails... currently I get our business name:
Please use the code below to confirm your email address and continue on Globacap Technology Limited
Hello team, we have a problem with the migration to the new package version, we are currently using "@kinde-oss/kinde-auth-nextjs": "^1.8.24",
and we are trying to migrate to "@kinde-oss/kinde-auth-nextjs": "^2.4.6" . We use Next.js 14v with page router. We did the migration based on https://docs.kinde.com/developer-tools/sdks/backend/nextjs-prev-sdk/. But we constantly get error 500 related to the session as in the picture below.
Hello! I'm evaluating Kinde for our organization, and I have a simple question about SAML connection pricing.
I tried using the AI for answering the question, but it gave contradictory answers - figure I'm better off asking here then. 🙂
It's pretty simple really: given I haven 3 organizations, and these all wish to sign in to my application using their own Entra ID configuration, would this be considered 3 unique connections, thus costing $50 (1 being free, and 2 more for $25 per connection on Plus plan)?
Hi, I have two applications: a mobile app (Android) and a web app (built with Next.js). Users log in to the mobile app, and on one of the screens, there’s a button that redirects them to the web app. I want the users to seamlessly access the web app without needing to re-authenticate, as they are already logged into the mobile app. I attempted to use the token exchange grant type to achieve this, but it doesn’t seem to be supported.
Could you suggest an approach or solution?
And the background image still works
Our test env does still contain the correct logo, so our new website must be unrelated (i tought perhaps we used a link and the logo on our website changed)
Hi,
Since we launched our new website (not the portal that uses our login). But this may be unrelated.
Our logo does not longer work in kinde. The alt tag is displayed.
I already tried reuploading the logos.
Hi! I've been reading the Next.js Pages Router documentation, and am confused about a few things:
app/layout.tsx
; that looks like an App Router thing, not a Pagers Router?Auth
component, but I don't see what that is (or the code for it)?/oauth2/token
endpoint from a Hono.js server (running in a Bun environment) and am getting a 502 Bad Gateway response. This is my code:import { Hono, type Context } from "hono"; import { GrantType } from "@kinde-oss/kinde-typescript-sdk"; const api = new Hono(); api.get("/my-route-path", async (c: Context) => { const url = new URL(c.req.url); const authCode = url.searchParams.get("code"); const response = await fetch(`${KINDE_SUBDOMAIN}/oauth2/token`, { method: "POST", body: JSON.stringify({ client_id: KINDE_CLIENT_ID, client_secret: KINDE_CLIENT_SECRET, grant_type: GrantType.AUTHORIZATION_CODE, redirect_uri: KINDE_REDIRECT_URL, code: authCode, }), headers: { "Content-Type": "application/json" }, }); });
{ ok: false, url: "https://my-kinde-subdomain/oauth2/token", status: 502, statusText: "Bad Gateway", headers: Headers { "date": "Tue, 14 Jan 2025 02:03:49 GMT", "content-type": "text/html", "content-length": "122", "connection": "keep-alive", "server": "awselb/2.0", }, redirected: false, bodyUsed: false, Blob (122 bytes) }
/oauth2/token
endpoint from a Hono.js server (running in a Bun environment) and am getting a 502 Bad Gateway response. This is my code:import { Hono, type Context } from "hono"; import { GrantType } from "@kinde-oss/kinde-typescript-sdk"; const api = new Hono(); api.get("/my-route-path", async (c: Context) => { const url = new URL(c.req.url); const authCode = url.searchParams.get("code"); const response = await fetch(`${KINDE_SUBDOMAIN}/oauth2/token`, { method: "POST", body: JSON.stringify({ client_id: KINDE_CLIENT_ID, client_secret: KINDE_CLIENT_SECRET, grant_type: GrantType.AUTHORIZATION_CODE, redirect_uri: KINDE_REDIRECT_URL, code: authCode, }), headers: { "Content-Type": "application/json" }, }); }); This is the error response that I am getting:
We will update the status page with a short post mortem by the end of the next business day
Will there be a post mortem?
Confirmed it’s working.
Email sending issue has been resolved. Apologies for the delay we were focused on fixed.
Checking in again now that it’s been another hour. Is there an ETA?
Any estimate or info? This is a major issue
email,id,email_verified,first_name,last_name,hashing_method,hashed_password user.name@domain.com,ANid,TRUE,Name,LNameD,bcrypt,PASSWORD
I am experiencing the same issue