This feedback stems from this support discussion - https://discord.com/channels/1070212618549219328/1308303315595165777/1308303315595165777.

It includes use-case and current work arounds. Would it be possible to have an option to remove the Register button from Kinde's login experience when going through the designer? It seems like a low-effort (not that I have to do the work 😅) enhancement that circumvents a whole lot of gymnastics developers need to go through for some of the registration experiences. It also reduces the need for potential custom registration / login experiences.

This support post is in relation to https://discord.com/channels/1070212618549219328/1308179325752705145 as to not confuse or deviate from what the OP of that thread was after.

Currently for registrations I am using Kinde's out of the box registration experience with a twist. I basically ask a few questions, store the answers, and then kick off Kinde's out of the box registration workflow. Once registration is completed I resume the process with follow-up questions before completing my applications setup which includes storing details (including correlating the Kinde data with my data) and setting up the organisation using Kinde's Management API. (I don't want to just auto create orgs)

This is great because by using Kinde's out of the box workflow I don't need to write code to log in or register. But I can still have custom activities before and after the Kinde part of the process.

However, if a user were to click log in, and then register on the Kinde UI they would have been registered in Kinde but not through my onboarding process resulting in an incomplete setup. Now, I could potentially detect this when signing in and get them to have a slightly different onboarding experience but then I'd need to maintain two different onboarding workflows both in terms of code, but also customer support.

As per the advice Yoshify gave in the original thread, you can disable self sign up, but then Kinde's registration functionality will return a 404 (not found / supported) error.

Is it possible in the brand design screens to somehow remove the register button from the login experience?

I've been scratching my head for the last hour or so. I can't authenticate, even though it's been working fine previously. I haven't changed any code related to authentication since it was all working fine yesterday.

I am able to get to the point where Kinde accepts the username / password but it looks like it's unable to hit Kinde's /api/callback URL (which is what Nuxt uses)

I just get a very generic error message (see attached) which doesn't really help much. I have restarted the browser, used a different browser. Cleared out my cache / cookies. Tried registering and then logging in, etc, and nothing works (the registration works but then it fails to log in).

I've checked I'm using the latest version of Kinde's Nuxt library and that my environmental settings for Kinde are still correct.

There isn't anything obvious in the audit and I can't even see the login attempts there. Only the registration audit events.

What can I do to troubleshoot this?

Hi, I'm trying to add some scopes so that I can use the Kinde API through M2M. My backend for this is .NET but I'm not able to generate a token so I've also tried through Postman. Every time I try to supply a scope when authorising I get something the along the lines of The OAuth 2.0 Client is not allowed to request scope 'read:users'. I have checked that my application is authorised and read:users is enabled in the Kinde admin UI. I am using the audience as per the Kinde UI. Not supplying any scopes allows me to authenticate, but obviously actual API calls fail as I don't have any scopes in my access token. Is there something else I am missing?

I think there's a bug with the Kinde API when it comes to looking at scopes. Kinde's Management API doesn't work with the default way that Postman handles scopes for instance. If you supply the scopes in the body (default) Kinde will complain saying that the scopes are invalid. However, if you supply them in the headers, it will work.

I'm using Nuxt for my web application and when creating the onboarding experience I'm trying to use the default Kinde registration experience out of the box as much as possible. There's two possible 'account types' on my platform and what I want to do is redirect the user to a URL based on an earlier step. Based on that, I set the post_login_redirect_url.

E.g.

<RegisterLink post_login_redirect_url="/registration/register-service-provider" :is_create_org="false"> <v-btn>Register</v-btn> </RegisterLink>

However, it doesn't look like this URL is being respected and it is going to my default redirect_url after registration. (It is respecting is_create_org though).

I have also made sure that the redirect URL is available in the Kinde app registration as well. Is there something I am doing wrong?