Orchard Core is an open-source modular and multi-tenant application framework built with ASP.NET Core, and a content management system (CMS) built on top of that framework.
I am working on an application that uses orchard core for its versioning and multi-tenant possibilities.
I encountered an issue during the upgrade of orchard core from 1.0.0-rc2-13450 to 1.0.0(issue) that was making my tenants unusable, but was resolved by going into each tenant's admin and resaving the configuration found in OpenId Connect -> Settings -> Authorization Server.
I thought this issue only appeared because of the upgrade, but I discovered that when I add new steps to a cms data migration(for example modifying a content type) and orchard core needs to update its entities the same problem occurs.
Orchard core modifies the "OpenIdServerSettings" section in the Document table, Orchard.Core.Settings row of each tenant and makes it unusable, because the cms then cannot properly read the open id settings until I go perform the configuration resave I mentioned before in the admin panel.
How my tenant's recipe.json open id server settings section looks:
How the working tenant settings look in the database:
How the tenant settings look when updated by orchard core(not working):
I am not sure what is causing this update, please let me know if there is something I need to modify in my recipe or if you have any ideas.
Hello,
I am working on an application that uses orchard core for its versioning and multi-tenant possibilities. I encountered an issue during the upgrade of orchard core from 1.0.0-rc2-13450 to 1.0.0(issue) that was making my tenants unusable, but was resolved by going into each tenant's admin and resaving the configuration found in OpenId Connect -> Settings -> Authorization Server. I thought this issue only appeared because of the upgrade, but I discovered that when I add new steps to a cms data migration(for example modifying a content type) and orchard core needs to update its entities the same problem occurs. Orchard core modifies the "OpenIdServerSettings" section in the Document table, Orchard.Core.Settings row of each tenant and makes it unusable, because the cms then cannot properly read the open id settings until I go perform the configuration resave I mentioned before in the admin panel. How my tenant's recipe.json open id server settings section looks: How the working tenant settings look in the database: How the tenant settings look when updated by orchard core(not working): I am not sure what is causing this update, please let me know if there is something I need to modify in my recipe or if you have any ideas.
Thank you, Vlad S.