Hi @Komal Singh ,
- the relationship between KMSI and the Refresh Token API is that they both allow users to remain signed in to your application. KMSI enables users to remain signed in even after they close the browser, while the Refresh Token API allows users to obtain a new access token and refresh token pair after the current access token has expired.
- For a seamless e-commerce experience, it is recommended to use KMSI and implement a silent login using the Refresh Token API. Silent login does not redirect to Azure AD B2C, but instead uses the Refresh Token API to obtain a new access token and refresh token pair without prompting the user to enter their credentials. This approach provides a seamless experience for the user and allows them to remain signed in to the application even after the access token has expired.
- If KMSI expires, the recommended strategy is to call the Refresh Token API to obtain a new access token and refresh token pair. This will allow the user to remain signed in to the application without being prompted to enter their credentials again. Calling the Refresh Token API after KMSI expiration will not result in an error, and you can refresh the token even after KMSI expiration.
For a seamless e-commerce experience, it is recommended to use KMSI and implement a silent login using the Refresh Token API. If KMSI expires, you should call the Refresh Token API to obtain a new access token and refresh token pair. More info here.
Please let me know if you have any questions and I can help you further.
If this answer helps you please mark "Accept Answer" so other users can reference it.
Thank you,
James