Describe the bug
When using tryLoginCodeFlow, the Success event triggered does not have any information about what the login options were (including the state) in order to route. tryLoginCodeFlow also doesn't call onTokenReceived even though it shows deprecated
Expected behavior
tryLoginCodeFlow should have context about the login on successful token grab, either via the events or onTokenReceived.
Additional Context
I use the initLoginFlow with a string passed in. This should be passed back to the tryLogin call after token received.
The existing preserveRequestedRoute is pretty limited in what you can do before routing, like get the user info.
Describe the bug
When using tryLoginCodeFlow, the Success event triggered does not have any information about what the login options were (including the state) in order to route. tryLoginCodeFlow also doesn't call onTokenReceived even though it shows deprecated
Expected behavior
tryLoginCodeFlow should have context about the login on successful token grab, either via the events or onTokenReceived.
Additional Context
I use the initLoginFlow with a string passed in. This should be passed back to the tryLogin call after token received.
The existing preserveRequestedRoute is pretty limited in what you can do before routing, like get the user info.