Problem
The configuration of the Microsoft Teams Connector is unable to proceed beyond the configuration of the Source tab.
Note: It has been confirmed that the information below is correct:
- X509 Certificate Thumbprint
- Application ID
- Application Secret/Key
When hitting the 'Next' button the login to Microsoft Online is connected and the permissions requested for the Organization, but the Connector configuration just returns to the Source tab and the wizard is unable to proceed further.
Error Message
There is no error displayed in the User interface. However, the wizard is stuck in an endless loop until the connector is exited.
Review of the Merge1 logs show the following:
2022-03-03 16:51:01,873 [16] INFO Merge1.Portal.Controllers.ConfigurationController - OAuthCallback started...
2022-03-03 16:51:01,873 [16] INFO Merge1.Portal.Controllers.ConfigurationController - State: ''
2022-03-03 16:51:01,873 [16] ERROR Merge1.Portal.Controllers.ConfigurationController - Can't find current connector.
2022-03-03 16:51:01,877 [16] ERROR Merge1.Portal.Controllers.ConfigurationController - Error on OAuthCallback. UserID=0, RequestRawURL=/Configuration/OAuthCallback?admin_consent=True&tenant=788b1984-3887-4f80-b53d-2b98d513f61b
System.InvalidOperationException: Unexpected error, connector should not be null at Merge1.Portal.Controllers.ConfigurationController.OAuthCallback()
2022-03-03 16:51:01,878 [16] INFO Merge1.Portal.Controllers.ConfigurationController - Ending OAuthCallback...
Cause
This issue can be caused when the Admin Console is being accessed via a different URL than what was configured during application registration for the Redirect URI.
For Example:
The Admin Console is being accessed via URL https://192.168.2.107/Configuration.
The Redirect URI configured in Azure Active Directory during application registration is using https://MergeSRV.Merge1.com/Configuration.
Solution
To resolve this issue access the Admin Console using the same URL that is configured in the Redirect URI during application registration in Azure.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.