0
I’m working with Google Drive API and localhost the Consent screen - the one you authorize the application to make changes and view your data - normally opens in a new browser tab.
But when I move the project up to Azure when I click on the button that opens this consent screen nothing happens. I already checked and the action is coming in the code correctly but this locking this part because it is waiting to open a new tab for the person to confirm, and nothing happens.
Does anyone know if there is a security system in Azure that doesn’t allow opening new tabs or redirecting to external links?
Vc has set up in Google to receive requests not only from your machine, but also from the domain your application is hosted in Azure?
– Thiago Lunardi
So what happens is this, the application runs on a virtual machine in Azure. Now in the Google settings, I sometimes set the wrong things but still it opened the authentication tab but indicating that an error occurred (this in localhost), but when putting in Azure nor this tab indicating error opens, now I do not know if this work(from opening tab indicating error) is only supposed to happen on localhost or if on Azure it should also be opening, and I also don’t know if I should set up something on IIS to allow the application to open this login page.
– Brayan