I was about to try and make a collection of components for the NextJs SDK for the custom signin and signup. When the feature was released it was hard for me to make it work the way I wanted. So It’d be cool to have that.
I could help on that too as I was interested in doing it in the first place
I think it would also be super cool to have a starter with the webhook to handle request to the database when authenticating as the feature was super in demand.
Not an active user yet you may ignore it but protected routes sounds to be like a neccessarity to me I think.
Need an efficient way to store the authenticated and signed up users in a database after registering. ( I believe this can be done w management api) Like mongo db. Loving kinde btw!
More customisation of the Kinde authentication screens would be really nice. One issue I'm currently faced with is wanting to remove the "create account" button from the sign in page while still being able to allow users to self sign up.
We have quite a specific flow since our application is invite only through enterprise clients, but this creates a potential flow where our invited users could accidentally create an account at the wrong point.
We could address this by building a custom page, but right now we don't have the capacity to, and we'd really like to keep Kinde's external page opening as part of our flow to effectively demonstrate our auth flow in full.
Examples of protecting routes in the app router without using middleware. I feel like there are paradigms using pages, layouts and route groups that are much more clear and do not incur additional runtime costs or elusively effect bundle files.
Ready to help with Finnish language implementation
I feel like you may still be at a point where you need to be focusing on supporting what you have already, rather than new things. I've been struggling a bit with slow/inaccurate support here, plus a lack of documentation for existing features,, and somewhat poor documentation for the Nextjs SDK. Poor docs can be worked around with good support, and vice-versa, but I'm struggling with both 🙁
I thought I've read somewhere that having your route protection on layout level isn't ideal
More libraries and more documentation for libraries. Like there’s a typescript library or a node library (that uses express for all examples) and it’s not completely clear which to use or how to set things up for a node/deno/bun app using hobo or Elysian or anything like that.
And in the front end you have the react library, the typescript library, and the pkce library. It I’m setting up a qwik or solid app, which should I use? Pkce but there’s no sufficient docs.
For iOS, the library uses cocoa pods, but cocoa pods disrupts the entire project. Cocoa pods is outdated and replaced with the swift package manager and the docs include the app delegate and UIKit which no one uses anymore. So this is just really outdated.
If there’s up to date libraries, and you to date complete docs, the community will make guides and write blog posts etc
Love your profile pic haha
Fun way to present yourself +1 !
To clarify, are you proposing moving further up to doing auth in page.ts files or advocating for using middleware?
I don’t like how middleware are done in NextJs. So yeah to put it in page.ts. It is a pattern that is used a lot even with other authentication clients
Heyy is it possible to restrict single access login. Meaning only 1 active authenticated session per user
