REST API reliability challenges in Azure
For those of us that are software developers, we are accustomed to this message.
"The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. T...
Forum Discussion
We heavily use the REST api to retrieve financial data. Recently our onestream platform was migrated to Azure and we started receiving failures that never occurred on-premise.
Here is a third error that started affecting us in Azure, but did not ever occur on-premise.
System.Exception: 'Invalid response from query in SendHttpRequest. Status code is Unauthorized. Content is "Error processing External Provider Sign In information. The remote name could not be resolved: 'login.microsoftonline.com'". '
This occurs AFTER we have used the AAD to authenticate and calculate an oauth bearer token. It happens within the subsequent request to the REST api. What this is essentially saying is that the onestream application server in Azure is not able to contact "login.microsoftonline.com". Or rather, it can't even resolve the I.P. address for login.microsoft.com.
Obviously it is a problem if/when any application that is hosted in Azure is unable to contact an identity server that is also hosted in Azure. I'm assuming the purpose of contacting that identity server is to validate the oauth bearer token in the request header.
If anyone is familiar with this error, or with the resolution, please let me know. Migrating our onestream platform to Azure has been an interesting experience, with quite a few challenges. We are opening support tickets as well, but new problems seem to be coming up faster than we can fix them. If onestream support is able to find fixes to these, I will remember to circle back with a reply for the forum.