In order to enable Anonymous service for .Net Core edition of Creatio all you need to do is to add information about this service to "AnonymousRoutes" block of ..\Terrasoft.WebHost\appsettings.json file.
The documentation clearly says that there is way to create a configuration service with Anonymous authentication. Hope you went through the Academy link I pasted in the question.
My question was -
The documentation only lists out the steps for the WCF based configuration services (Used by .Net Framework on Windows). How does one go about creating an anonymous service on a Linux installation of Creatio using .Net Core?
In order to enable Anonymous service for .Net Core edition of Creatio all you need to do is to add information about this service to "AnonymousRoutes" block of ..\Terrasoft.WebHost\appsettings.json file.
Please shed some light on LDAP integration with .NET core. We plan to use .NET core on a Linux box. Does it work OOTB seamlessly as it does with the .NET framework versions? Are there any architectural implications/extra components that need to be deployed?
Please explain the below phrase that has been picked from the .NET Core Creatio documentation.
"LDAP Integration - Current Implementation - A separate .NET Core instance is used for the synchronization of Windows-based applications. "
There is no possibility to establish LDAP integration with Creatio that is fully deployed on .Net Core platform because of .Net restrictions. This kind of integration is planned after the implementation of corresponding functionality on .NET 5.
Speaking of the "LDAP Integration - Current Implementation - A separate .NET Core instance is used for the synchronization of Windows-based application". This means that you can deploy a web-farm that will have several nodes and one of them should be on Windows. Then this Windows-based node should be used for LDAP integration.
A quick clarification on LDAP integration with web farm setup.
Say, I have 2 nodes running in the .Net framework, Do I need to perform the LDAP setup in both nodes and update the required web.config files in both nodes?
Is there a way to figure out if a particular plugin supports .Net core on the marketplace? I have a use-case where I am leveraging Creatio's .Net core platform capabilities and installing it on-premise on a Linux box and want to ensure that I make the right choice of plugin from the marketplace.
It would be great if the marketplace team could introduce an indicator against each plugin on the marketplace to let the community know if support is offered for .Net Core or not.
We have registered a request to add some "markers" for each marketplace application which will show Creatio configurations this application is compatible with.