How can we integrate the SignUp component from the SDK in to the Gate App

[brionmario]

Since we now don't forward the applicationId to the sign-in page when an authorize request is made, how can we handle the SignUp when redirected from the Sign In page.

Since Registration requires to send the applicationId in the payload.

{
  "applicationId": "d8531775-0fdb-4b13-af74-46e26f27cc19",
  "flowType": "REGISTRATION"
}

[senthalan]

It was caused with this change #624, I have removed the applicationId from the login page redirection. If it is needed for the registration flow, we can add it back.

[senthalan]

Taking a step back, won't the /flow request return the applicationId ? @ThaminduDilshan

In a way, I like to keep this url minimal. (We have to remove the sessionDataKey too and keep only the flowId)

[ThaminduDilshan]

We should be able to allow self registration by adding the applicationId to the initial flow response or the authz response. This will allow the users to self register, but when someone clicks on self register, they'll be starting a new flow with a new flow id.
When the registration is successful, we won't be able to continue the OAuth authentication as it's a different flow.
We'll need to do some customization to allow this.

Same concern will be there with recovery flows as well. In order to resolve this, ideally we should be able to switch the flow type in the middle of a flow.

In our initial requirement gathering for the flow engine, we had a use case where a different flow (graph) can be initialized/ called from another flow (graph). This ideally addresses the above concern.

[darshanasbg]

Is this sorted @brionmario @ThaminduDilshan?

We need to have signup flow working for the oauth flows in the 0.12.0 release.

[brionmario]

Not yet. @ThaminduDilshan FYI

[brionmario]

This is sorted!