TotalScrub
KKinde
•Created by TotalScrub on 12/23/2024 in #💻┃support
Refresh claims approach
Hi, I'm trying to figure out how to refresh claims / user details with Kinde. There are few scenarios I'm trying to solve this for:
- As part of registration activities a user might be allocated to an organisation & role via the M2M API. Their original access token doesn't have these claims and they end up with forbidden access. I understand the why as the Nuxt server is using the cached values.
- Users might have their roles changes within an admin section using the M2M API.
If I log the user out and in again, it works fine. If I refresh the claims using
refreshUserClaims() in the management API (either via the JavaScript SDK or .NET SDKs) then nothing happens and the user still gets forbidden access issues from my application (I do get a success response from Kinde when calling the refresh API).
With Kinde, how are you supposed to handle this? Ideally without logging out and in again.20 replies
KKinde
•Created by TotalScrub on 11/19/2024 in #💻┃support
How can I have a distinct login & registration experience without custom UIs?
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?
12 replies
KKinde
•Created by TotalScrub on 11/12/2024 in #💻┃support
Something went wrong - Is there an outage?
5 replies
KKinde
•Created by TotalScrub on 11/4/2024 in #💻┃support
Having problems with supplying scope to Kinde API
5 replies
KKinde
•Created by TotalScrub on 10/24/2024 in #💻┃support
Registration post_login_redirect_url
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?5 replies