The connection string format shown below is to be used with Loome Publish. You will need to replace a few pieces of information within the connection string;
• Server FQDN – This is the fully qualified domain name of the SQL server where your database is hosted.
• Database Name – The name of the database used during the database creation process.
Ensure you remove the <> values from the string, these are just to highlight tokenized parts of the connection string.
Server=<Server FQDN>;Initial Catalog=<Database Name>;Integrated Security=true;TrustServerCertificate=True;Pooling=False;MultipleActiveResultSets=False;Encrypt=True;Connection Timeout=30;
These keys are required for Loome Publish to function correctly. They must be entered during the application installation.
|ClientId||This is the Application ID of the App Registration created during Active Directory app registration.|
|Appkey||This is the App Key generated during Active Directory app registration. You cannot go back and retrieve this afterwards. If you did not save the App Key, you will need to generate a new App Key.|
|PostLogoutRedirectUri||This is the URL of your web application followed by a trailing forward slash. (Ex. https://portal.my.domain/)|
|Tenant||Look under your Azure Active Directory > Domain Names > And locate the .onmicrosoft.com domain name.|
|TenantId||Look under your Azure Active Directory > Properties > Directory ID.|
|BiPortalDb||This is a SQL connection string for your web application. Please refer to SQL Connection String Format when entering this value.|
|BiPortalDb_DatabasePublish||This is a SQL connection string for your web application. Please refer to SQL Connection String Format when entering this value.|
These reply URLs are required for Loome Publish to function correctly. You will need to replace <my.site.name> with the configured DNS name of your IIS website and put these in the reply URLs section of your Azure App Registration.