I implemented external login to umbraco backoffice 7.14 following shawazza article https://shazwazza.com/post/configuring-azure-active-directory-login-with-umbraco-members/ but get very confusing situation after deploying to environments. On dev env everything is fine but on uat is missing some cookies: main are ai_user and ASP.NET SessionId. What do you think it could be problem with env configuration or Azure Active Directory app ?
Related
I have deployed the verdaccio container in APP service and sucessfully deployed and able to login. Now question is how to integrate with Active Directory to login to verdaccio?
I have tried to mount the configuration file with active directory configurations but it is not working.
I have just deployed my .net core and react project on Azure using web deploy and published using Windows instead of Linux. I seem to be getting a HTTP Error 500.30 here are the error logs below, I have used the pre configured identity server 4 when making the application but I assume the error has something to do with this, anyone know of a fix for this?
Error log
Error log 2
I'll assume that this app works in your development environment, so I think this is a configuration error.
ASP.NET Core have 3 default environments: development, staging and production; and you have differents appsettings for each of them (appsettings.json wich is the base, appsettings.Development.json, appsettings.Stating.json and appsettings.Production.json).
My theory is you have the configuration related to IdentityServer only in appsettings.Development.json, so this is not beign loaded in production environment.
Include the configuration in appsettings.json or appsettings.Production.json an check it out.
If you're deploying the app to Azure AppService you could include the config in the AppSettings section.
Check more about config and enviroments:
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-3.1
I've solved the problem it did have something to do with my appsettings.json where i needed to include "Key": {
"Type": "Development"
},
I managed to deploy my react app with an Azure CD pipeline on an Azure App Service. And the pipeline throws no error.
Unfortunately when I click browse on the Azure app service I get this message "You do not have permission to view this directory or page."
I enabled advanced logging and here is what I get:
Here is my web.config file content:
[![enter image description here][2]][2]
Any hint on how to solve this issue?
You do not have permission to view this directory or page
The root reason is that there is no default page in your Azure website. You can try to directly view the page with following url.
https://{siteanme}.azurewebsites.net/views/login.html
Or you could add the default document in the project root folder and set it as default page in appsetting on the Azure portal and save the setting.
The default document is the web page that is displayed at the root URL
for a website.
In addition, you can check the IP restrictions or authentication settings on the Azure web application that may block you.
Check Web App > Authentication /Authorization and Web App > Networking > Access Restrictions
Here is a blog about deploying create-react-app on Microsoft Azure, you can refer to.
Created the production build by executing npm run build command. A
build folder got generated in the solution with some meta data files
Once connected via the FTP client, copy the entire content of the
build folder created earlier into the /site/wwwroot/ folder on your
Azure Website
I needed to configure the following in Azure Web App Configuration:
index.js as a Default Document
change the virtual path to \site\wwwroot\build
I have a nextjs react website running fine locally, after I ran 'next build' I got a .next file. I tried uploading the contents to azure app services but when I visit the URL I get an error that I don't have permission to view this page.
From googling the issue I've found that I need to install something on the azure app service: https://github.com/MRCollective/nextjs-server-azuresiteextension - "Install the nextjs-server site extension (either via the Portal or programmatically via ARM)" but I don't understand what that means or where I can find it (extensions in portal and site extensions does not have nextjs-server)
I've got a web app with asp.net Core 2.0 and ReactJS.
If I publish the app in Azure in a Production environment everything goes right.
But when I try to change it to Development (adding on the Application Settings the key ASPNETCORE_ENVIRONMENT with value Development) the app crashes at the startup.
More exactly on the Configure method trying to do this:
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
app.UseWebpackDevMiddleware(new WebpackDevMiddlewareOptions
{
HotModuleReplacement = true,
ReactHotModuleReplacement = true
});
}
And it throws an error like this:
An error occurred while starting the application.
AggregateException: One or more errors occurred. (Attempt to connect to Node timed out after 60000ms.
)
System.Threading.Tasks.Task.GetResultCore(bool waitCompletionNotification)
NodeInvocationException: Attempt to connect to Node timed out after 60000ms.
Microsoft.AspNetCore.NodeServices.HostingModels.OutOfProcessNodeInstance+d__13.MoveNext()
I tried to publish it locally but is the same that in Azure.
Any one could help me to configure it correctly?
Thank you.
We host our site in Azure as well and the solution for me was to add this config key/value to the Application settings.
Key: WEBSITE_NODE_DEFAULT_VERSION
Value: 6.9.1
I suppose you could also add it to your appsetting.json or web.config as well.
ok after a long struggle I have found a way to overcome this issue.
First set the app settings in Azure WebApp Settings - WEBSITE_NODE_DEFAULT_VERSION with the latest version. In my case I have used the node version 8.9.4 matching my dev machine environment.
The Azure deploy task in VSTS has got a feature to run a script post deployment where we can run "npm i -g" which will pick the package.json file from the wwwroot folder.
Try this and update here.