mgt not working in production.

[Jio-AL]

Hi, I used this sample in my development environment and I have created a project using these mgt controls. So far they work great, but I just deployed into production, in a hosting service, and the project I created doesn't work. So, I tried to deploy this sample into production to verify if this is the issue, and it is. The home page load well, but after I click the login button, the url shows the login.microsoftonline.com/common/oauth2/... authentication and then when it gets back shows the error page: /Home/Error. It is showing the warning page that it is in Development Mode and I couldn't make it to show the error details, even changing the ASPNETCORE_ENVIRONMENT to Development in web.config.

Also, I have created a sample Core Web App project connecting to Azure AD using the same App Registration in Azure and this worked well, so the connection using the App Registration is ok.

The log file shows:
=GET / - HTTP/1.1 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/109.0.0.0+Safari/537.36+Edg/
=GET /api/Proxy/v1.0/me HTTP/1.1 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/109.0.0.0+Safari/537.36+Edg
=GET /Account/SignIn -
=POST /signin-oidc https://login.microsoftonline.com/
=GET /Home/Error https://login.microsoftonline.com/
=GET /api/Proxy/v1.0/me - /Home/Error

Do you know or have any ideas what is happening to mgt in production?

Thanks,
Jio

[sebastienlevert]

Can you share a repro that would highlight this issue? I assume the client id and potentially tenant id are the right ones? I see you are using the proxy provider (from the GET call). Is that the case?

[sebastienlevert]

The link to the sample you shared is not using the Microsoft Graph Toolkit. I'm a bit confused... If you could post in a repo so we can have a look I'd appreciate it.

Also, are you getting any errors in the console?

[Jio-AL]

I'm so sorry, I just realized it is not, but it gets the same issue (doesn't works in production).

This is the correct one, I just added my Client Id and Secret:
https://github.com/microsoftgraph/microsoft-graph-toolkit/tree/main/samples/proxy-provider-asp-net-core

Also, I have uploaded it in a repo https://github.com/Jio-AL/mgt-netcore

This is the warning message I got in console, but I got it in my local pc as well, and it works anyway:
mgt-loader.js:55
A parser-blocking, cross site (i.e. different eTLD+1) script, https://unpkg.com/@microsoft/mgt/dist/bundle/wc/webcomponents-loader.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message. See https://www.chromestatus.com/feature/5718547946799104 for more details.

Thanks!

[sebastienlevert]

Ok, if this is the only error you are getting from the console, it's a good start. I'll hand it over to @musale @Mnickii or @gavinbarron to have a look at the repro or if they have any hints they could share! Thanks!

[Jio-AL]

It is ok now. My bad. I published it in an azure web app so I can have the log and see the error in detail, instead of the limited error log of the hosting provider. So, this was my bad, I misunderstood your suggestion about the url, I added in the Azure App Registration, but I needed to update it in the appsettings.json file as well. Everything is working good so far.
Thank you for your time on this!

[gavinbarron]

The underlying issue was incorrect configuration of the application due to missing settings in appsettings.json.

Correcting the configuration resulted in a working application