A few troubleshooting steps to consider with the integration between VIP and OWA

Products

• VIP Service

Issue/Introduction

Customer have made the necessary settings for VIP to use 2FA on Exchange (OWA). You can see all the settings as a screenshot in the attachment. However, even though the secure code appears on the OWA screen, users can log in to the exchange regardless of whether they fill it in or not. There's probably something wrong, but we couldn't find out what it was. We ask for your support.

Environment

VIP Service

Resolution

It seems like the secure code is appearing as expected on the OWA screen, but it is not enforcing the two-factor authentication for users. This could indicate a configuration issue or a problem with the integration between VIP and OWA.

Here are a few troubleshooting steps to consider:

1. Ensure VIP is properly configured in Exchange: Double-check that the Exchange (OWA) settings are correctly configured to enforce the 2FA requirement through VIP. There might be a policy setting or configuration that's allowing users to bypass the 2FA prompt. Refer: techdoc

2. Verify the OWA Customization: Review the modifications made to the OWA file, as any issues or conflicts in these changes could result in the 2FA prompt not being enforced correctly. Probably this link may help. This link is based on my research and not official documentation from Broadcom.

3. Authentication Policies: Confirm that the Exchange authentication policies are correctly aligned with the VIP 2FA integration, ensuring that they are not set to allow fallback to password-only login. VIP supports the two authentication methods See link.

4. VIP Logs: Check the VIP logs to see if the 2FA verification attempts are being processed as expected. This might give us further insight into whether the request is being handled properly on the VIP side. Refer to this VIP Enterprise Gateway Troubleshooting Guide to enable and analyze logs.