Passing params from loginWithRedirect to the new Universal Login

[dan.woda]

@justin7

So the first usecase is that we are doing a lazy login/create account. We allow customers to search for the product they want and ask them to create an account (or log in if they are not already) during the “checkout” process. In this case, we just wanted to pass along some information regarding the product they purchased.

For this you can use a state param to keep track of what the user was doing when they left the app to go sign in.

Prevent Attacks and Redirect Users with OAuth 2.0 State Parameters

@justin7

The second use-case is that there are 2 different audiences, one being a customer and the other being a provider of service and pending on which role you are in, I would like to have different messaging and fields in the create account experience.

For this, I would recommend passing a param as you described, then write a conditional statement in the Classic Universal Login customization page that changes the input options depending on the param you passed.

Lock UI Customization