Oqtane 3.1 IIS Deployment

[Sharafudeen]

Hi,

I've deployed Oqtane 3.1 to IIS but it is not working at all. Why it is creating appsettings.production.json & web.Release.config? Which configurations Oqtane can use it at runtime?

Also, whenever run oqtane with different urls (https://localhost:44357 or https://localhost:5000) Oqtane.Server.exe file then it creates Alias in the database.

The log shows, there is an issues in the following path,

1. \oqtane.framework-3.1.0\Oqtane.Server\Infrastructure\Middleware\JwtMiddleware.cs (line: 65)
2. \oqtane.framework-3.1.0\Oqtane.Server\Infrastructure\Middleware\TenantMiddleware.cs (line: 58)

[sbwalker]

Did you follow all of the instructions exactly as described here:

https://www.oqtane.org/blog/!/24/installing-oqtane-on-iis

Most issues related to installing on IIS are due to misconfiguration.

[Sharafudeen]

Actually we have xyz.com and I'm creating an application mysite under xyz.com/mysite. Mysite physical path is same as xyz.com application but mysite has different configuration such as Application pool and so on.

I really worries.. how Blazor and Oqtane didn't meet such requirements? Basically this feature should be there.. I'm planning to commit Oqtane in our organization but now thinking about alternative..

[sbwalker]

@Sharafudeen I am very confused by the following phrase in your last message.... "Mysite physical path is same as xyz.com" - are you saying that xyz.com and xyz.com/mysite point to the same physical location on disk? Does this mean that both xyz.com and xyz.com/mysite are running the same code? And is that code Oqtane?

[Sharafudeen]

Sorry.. No! I've created a folder "mysite" inside xyz.com site and it is configured as No Managed Code in the application pool but xyz.com site has different application pool and configuration.

[sbwalker]

@Sharafudeen here is a SO post of someone else having an issue with running Blazor in a sub application - https://stackoverflow.com/questions/62026817/deploy-blazor-app-to-a-iis-sub-application. It does appear to be possible but there would be a LOT of changes and testing required to support it in Oqtane, as it affects all static resources, tenant resolution, cookie authentication , etc....

I updated the IIS installation instructions to make some aspects more clear: https://www.oqtane.org/blog/!/24/installing-oqtane-on-iis

[Sharafudeen]

@sbwalker I can find the required places to modify but it will be customized Oqtane solution. I don't want to do that! I would like to keep Oqtane framework as an official release. This is because long-term maintenance! I would recommend, please make it Oqtane framework is more flexible such kind of use cases. Many of an organization might not allowed to create domain and open the port for "sub application" (In our case, we have more than 50 sub applications) and if they do it then they might have to invest for other setups such as security certificate, server maintenance, etc., There are indirect efforts and costs involved.. Hope you will understand.. Thanks!