Repository navigation
|
Currently everybody can register for our app using an URL posted on different websites. But the URL is the same on all pages, thus it is not possible to know where an user originated from after the sign-up. Is this possible? Or is there some other simple way to solve this problem? Any help or pointers are appreciated! Btw. someone asked a similar question already here https://stackoverflow.com/questions/58005895/is-it-possible-to-add-custom-get-parameters-in-keycloak-registration-page but unfortunately it was never answered. Thanks! |
Replies: 2 comments 7 replies
|
You could add a authenticator to your authentication flow for registration before the registration step, which reads additional get parameters from the request to the authentication session. After the user successfully registers another authenticator which follows the registration authenticator can persist this attribute with the user or somewhere else. |
|
Okay, thanks for the heads up! |
|
@bs-matil hello can you provide an example with the SPI implementation? |
|
hello can you provide an example with the SPI implementation? |
|
I am also still wait this for SPI implementation |
{{title}}
|
Can someone please answer this ? |
|
I'm developing for delivery projects. I don't know what an ISP is. If you'd like to tell me more, please write to me.
…________________________________
From: Harouna Diallo ***@***.***>
Sent: Friday, December 15, 2023 5:56 PM
To: keycloak/keycloak ***@***.***>
Cc: Javier Cañas [C] ***@***.***>; Comment ***@***.***>
Subject: Re: [keycloak/keycloak] How to pass custom attributes to the registration form? (Discussion #9449)
CAUTION - This e-mail originates outside of Dedalus. Be vigilant with content, links and attachments!
I am also still wait this for SPI implementation
—
Reply to this email directly, view it on GitHub<#9449 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5I5KRMLSZX275EVYLK4243YJS2PPAVCNFSM5LTIZJSKU5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TOOBWG44DQOI>.
You are receiving this because you commented.Message ID: ***@***.***>
|
You could add a authenticator to your authentication flow for registration before the registration step, which reads additional get parameters from the request to the authentication session. After the user successfully registers another authenticator which follows the registration authenticator can persist this attribute with the user or somewhere else.