By: ichrak gharbi user 29 Aug 2019 at 8:19 a.m. CDT

5 Responses
ichrak gharbi gravatar
I am trying to get users to register themselves for my application by using Gluu. So what I have provided a link to <domain>/identity/register where they can sign up, and this works fine. However the problem is that after the registration they are redirected to the Gluu "profile" page. If at all possible, I would like my users to be redirected to my webpage after registration. So, is this something that can be done?

By William Lowe staff 29 Aug 2019 at 8:26 a.m. CDT

William Lowe gravatar
I would write your own user registration page. The one built into Identity is not good for production use cases. See this [doc](

By ichrak gharbi user 29 Aug 2019 at 9:29 a.m. CDT

ichrak gharbi gravatar
It's not clear can you explain more ? thank you

By William Lowe staff 29 Aug 2019 at 9:33 a.m. CDT

William Lowe gravatar
For example, the page you used to register for your account on this portal.. its a custom registration page. The data gets sent into our Gluu Server. And then when you want to access this app, you authenticate via our Gluu Server. The documentation referenced above teaches you how to implement a similar process. This is better than using the default registration page you are referencing.

By Khaled Ghanem user 29 Aug 2019 at 10:07 a.m. CDT

Khaled Ghanem gravatar
Hey, I'm facing the same issue, and i don't know what to change or how to write my own page. Can you William provide us an example ? I don't need a lot of custom changes, just the same default page with redirecting to a specific url after registration. should i do it in the page here "/identity/register" ? Or is there a redirecting line of code that we can add to `postRegistration` method in `Configuration > Manage Custom scripts > User Registration > script`

By William Lowe staff 29 Aug 2019 at 12:30 p.m. CDT

William Lowe gravatar
Currently its hardcoded actually. Not the best design. I opened a ticket to address it in a future version: []( In the meantime, perhaps add an email activation sequence which will break up the process and result in the user not going directly into oxTrust. We updated our doc to explain how to add the email activation sequence: [](