Refused to frame 'https://website.kinde.com/' because an ancestor violates the CSP
Refused to frame 'https://canopyroofing.kinde.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self'".
I went through some of the discussions but could not figure out the solution. We will be embedding our app onto another app (We have a fixed domain.). Is there anything we can do at our app side or this need to if possible configured from Kinde side? ...picture / ext_provider claim inconsistent
ext_provider
to determine who facilitated the login (Google, Facebook or Kinde). At times this value is blank.
The problem is the picture
claim can be in different formats depending upon where it comes from. For example, from Facebook it is an entire JSON structure. Previously, in Auth0, the equivalent of a picture
claim was always a URL that we know we could use. Now, I have to determine if the ext_provider
is Facebook, because if it is, I need to parse the picture
claim and pull out specifically the URL and leave all the extra metadata provided.
The problem with this comes about sometimes when I login. On occasion there is no ext_provider
value. I think this is when I've already authenticated previously on Kinde so when I attempt to login, my request just goes right through. ...Unmatched Route
Attempting to commit invalid access_token token
🚨How to set up webhooks to make.com for new sign ups?
Cannot log into Kinde => authentication timeouts
Setting the audience for Nuxt to get token to be used with ASP.NET API
.env
file on my front end and I can get a token just fine. The issue is that the token doesn't have the aud defined (it's just an empty []
)
I have allowed the Kinde Management API access as per the instructions in the docs: https://docs.kinde.com/developer-tools/kinde-api/register-an-api/...next.js 14 hostinger vps nginx pm2 - CORS related issues
Entreprise SSO
Confused about Kinde implementation with Node/Express on the backend and React on the frontend
Next.js app router: is it safe to do the authenticated check in the layout?
isAuthenticated
check within the layout for all these pages?
My use of the middleware would be a little more complicated, since I'm already adding a CSP configuration there that needs to be applied to both protected and non-protected pages. So if this would also be a safe option, it would make it a lot more simple for me, but I'm not sure if I'm overlooking some security implications here. ...
503 after signup

IOS app review
"PropertyRequiredException: Issuer cannot be empty, js engine: hermes" error on Android APK
Kinde + tRPC + NextJS app router
Error not found /api/auth/login
Migrating MEAN web application (ExpressJS+MongoDB+AngularJS) to Kinde
Kinde + Supabase + WeWeb
Quick and Urgent about logout component
import { LogoutLink } from "@kinde-oss/kinde-auth-nextjs/components";
import { LogoutLink } from "@kinde-oss/kinde-auth-nextjs/components";