Wt

AuthWidget::processEnvironment should be called initially to process environmental information relevant for authentication.
The login state can become RequiresMfa if the user has a valid auth token and also has a Mfa step.
Checking whether the user also has a valid auth token is delayed until the widget is actually rendered, as part of createMfaView.
As a consequence, we cannot know whether the user will actually be logged in with a weak state until the widget is rendered.

If we were to listen for a loginChanged signal to know when the user is actually logged in from a MFA token, we would be notified of thus during the render step.
Applications might connect loginChanged signal to a function which clears the DOM tree and replace it with a logged in view.
However, this result in a JavaScript exception since the authentication widget was still being rendered.

It seems more appropriate that processEnvironment also checks for a valid MFA token.
This would ensure that the login state initialization from the environment is fully determined before the widget is rendered.
Applications can immediately render the correct widget (input MFA view or a logged in view), thus avoiding the JavaScript exception.