The problem: When using silent authentication, the mobile webview’s cookies are not refreshed. This results in the need to restart the interactive login flow. The B2C SSO will expire in a short time, in our case 15 minutes. After the expiry, there is no way to silent authenticate the SSO for mobile web views.
The solution: Provide a mechanism so that mobile silent authentication will also refresh the webview cookies. This will allow for a seamless flow for the mobile user. Most banking apps will now allow for biometrics with Face ID or Fingerprint ID. The user expects a seamless flow of all SSO components. The silent authentication is built into the MSAL mobile SDK. We need for this silent authentication to refresh the mobile web views in addition to the B2C token.
The problem: When using silent authentication, the mobile webview’s cookies are not refreshed. This results in the need to restart the interactive login flow. The B2C SSO will expire in a short time, in our case 15 minutes. After the expiry, there is no way to silent authenticate the SSO for mobile web views.
The solution: Provide a mechanism so that mobile silent authentication will also refresh the webview cookies. This will allow for a seamless flow for the mobile user. Most banking apps will now allow for biometrics with Face ID or Fingerprint ID. The user expects a seamless flow of all SSO components. The silent authentication is built into the MSAL mobile SDK. We need for this silent authentication to refresh the mobile web views in addition to the B2C token.