In order for WACI to be implemented the RP will need some way to link the client (not the wallet) to the response given to the wallet.
For use cases where a user is already signed in the challengeToken could contain some identifier for the user but it becomes trickier when it's a new user flow.
On the web you can establish a WebSocket connection, for mobile apps we need to collect some more information on existing patterns.
In order for WACI to be implemented the RP will need some way to link the client (not the wallet) to the response given to the wallet.
For use cases where a user is already signed in the challengeToken could contain some identifier for the user but it becomes trickier when it's a new user flow.
On the web you can establish a WebSocket connection, for mobile apps we need to collect some more information on existing patterns.