Application Connector to Azure is timing out

[jgruendike (Jeffrey Gruendike)]

Which IIQ version are you inquiring about?

Version 8.3

Share all details related to your problem, including any error messages you may have received.

I’m trying to add Azure (Entra ID) as a new Application and I’ve followed all steps in order to support certificate authentication. I haven’t been able to get Test Connection working and am running out of ideas. After a few minutes of waiting it will always return this error:

Test Connection failed with exception. Error message - Exception : OAuth2Exception [toString()=connector.common.oauth2.OAuth2Exception: Unable to generate access token. Response returned: org.apache.http.conn.ConnectTimeoutException: Connect to login.microsoftonline.com:443 [login.microsoftonline.com/20.190.190.129, login.microsoftonline.com/20.190.190.131, login.microsoftonline.com/20.190.190.195, login.microsoftonline.com/40.126.62.130, login.microsoftonline.com/20.190.190.196, login.microsoftonline.com/20.190.190.194, login.microsoftonline.com/40.126.62.131, login.microsoftonline.com/20.190.190.130] failed: Read timed out]

It simply times out and doesn’t show any other information. I cannot find anyone else in the forums who had this error and it’s not mentioned in any of the documentation I’ve seen. I verified that a firewall is not blocking any of the addresses in the error and can also connect to graph.microsoft.com. Any suggestions would be great. Thank you

[Remold (Remold Krol)]

Do you have a proxy configured?

How did you validate the firewall is not blocking?
My first test is using powershell on the IdentityIQ server:

Test-NetConnection graph.microsoft.com -port 443
Test-NetConnection 20.190.190.129 -port 443
Test-NetConnection 20.190.190.131 -port 443
Test-NetConnection 20.190.190.195 -port 443
Test-NetConnection 40.126.62.130 -port 443
Test-NetConnection 20.190.190.196 -port 443
Test-NetConnection 20.190.190.194 -port 443
Test-NetConnection 40.126.62.131 -port 443
Test-NetConnection 20.190.190.130 -port 443

This should work if there is a direct connection to the internet.

– Remold

[jgruendike (Jeffrey Gruendike)]

Those PowerShell commands all return True. I was hopeful it would be a setting somewhere but now I’m convinced our environment has another layer that’s blocking traffic somewhere. I’ve reached out internally to help troubleshoot. Thanks!