<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Configure the tool on RIA Docs</title>
    <link>https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/</link>
    <description>Recent content in Configure the tool on RIA Docs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CX Tables</title>
      <link>https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/configure-hazelcast/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/configure-hazelcast/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#overview&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The tool uses Hazelcast IMDG for clustering the runtime server JVMs. Even if only a single JVM is in use, you still need to configure the cluster name and network settings to avoid conflicts with other existing or potential Hazelcast configurations.&lt;/p&gt;&#xA;&lt;p&gt;For example, if the tool is installed separately for different environments, such as testing and production, each installation must have its own distinct cluster. This ensures that tasks submitted to one cluster, such as testing, do not execute on another cluster, such as production.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Configure security</title>
      <link>https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/configure-security/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/configure-security/</guid>
      <description>&lt;h2 id=&#34;user-and-role-maintenance&#34;&gt;User and role maintenance&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#user-and-role-maintenance&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The users and roles are maintained through the &lt;a href=&#34;../../docs/security/&#34;&gt;Security module&lt;/a&gt; in DIH.&lt;/p&gt;&#xA;&lt;h2 id=&#34;authentication&#34;&gt;Authentication&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#authentication&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;By default, user logins are authenticated against the &lt;a href=&#34;https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/configure-security/#local-authentication&#34;&gt;locally defined users&lt;/a&gt; in DIH. However, this configuration can be modified to authenticate against an &lt;a href=&#34;https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/configure-security/#ldap-authentication&#34;&gt;LDAP&lt;/a&gt; server or to use &lt;a href=&#34;https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/configure-security/#sso&#34;&gt;Single Sign-On (SSO)&lt;/a&gt;.&lt;/p&gt;&#xA;&#xA;&#xA;&#xA;&lt;style&gt;&#xA;    .alert {&#xA;        --bs-alert-bg: transparent;&#xA;        --bs-alert-padding-x: 1rem;&#xA;        --bs-alert-padding-y: 1rem;&#xA;        --bs-alert-margin-bottom: 1rem;&#xA;        --bs-alert-color: inherit;&#xA;        --bs-alert-border-color: transparent;&#xA;        --bs-alert-border:  var(--bs-alert-border-color);&#xA;        --bs-alert-link-color: inherit;&#xA;        position: relative;&#xA;        padding: var(--bs-alert-padding-y) var(--bs-alert-padding-x);&#xA;        margin-bottom: var(--bs-alert-margin-bottom);&#xA;        color: var(--bs-alert-color);&#xA;        font-weight: 400;&#xA;        background-color: var(--bs-alert-bg);&#xA;        border-left:4px var(--bs-alert-border) solid; &#xA;     }&#xA;    .alert-error {&#xA;        --bs-alert-color: black;&#xA;        --bs-alert-bg:  #FEF0F0;&#xA;        --bs-alert-border:#F15A5A;&#xA;      }&#xA;      .alert-warning {&#xA;        --bs-alert-color: black;&#xA;        --bs-alert-bg:  #FFF9EE;&#xA;        --bs-alert-border:#FF960A;&#xA;&#xA;      }&#xA;      .alert-success{&#xA;        --bs-alert-color:black;&#xA;        --bs-alert-bg:  #f2fff8;&#xA;        --bs-alert-border:#91eabf;&#xA;        }&#xA;        .alert-info{&#xA;            --bs-alert-color:black;&#xA;            --bs-alert-bg:  #E6F3FF;&#xA;            --bs-alert-border:#2685DA;&#xA;        }&#xA;        .alert i.fa-check-circle {&#xA;            color: #91eabf;  &#xA;        }&#xA;    &#xA;        .alert i.fa-info-circle {&#xA;            color: #2685DA;  &#xA;        }&#xA;    &#xA;        .alert i.fa-times-circle {&#xA;            color: #F15A5A;  &#xA;        }&#xA;        .alert i.fa-exclamation-triangle{&#xA;            color:#FF960A;&#xA;        }&#xA;&lt;/style&gt;&#xA;&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&#xA;    &#xA;    &#xA;    &#xA;             &#xA;        &#xA;    &lt;i class=&#34;fa fa-info-circle&#34;&gt;&lt;/i&gt;  &#xA;    &lt;span &gt;Regardless of the authentication method, authorization must be defined as described under &lt;a href=&#34;https://docs.riaproducts.com/dih/3.x.x/install/manual-installation/configure-the-tool/configure-security/#authorization&#34;&gt;Authorization&lt;/a&gt;.&lt;/span&gt; &#xA;&#xA;&lt;/div&gt;&#xA;&lt;h3 id=&#34;local-authentication&#34;&gt;Local authentication&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#local-authentication&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;If the property &lt;code&gt;com.ria.core.auth.store&lt;/code&gt; is set to &lt;code&gt;local&lt;/code&gt;, it indicates that logins will be authenticated against the local DIH user definitions. By default, the installation includes the user ID &lt;code&gt;ria&lt;/code&gt; and the password &lt;code&gt;ria00&lt;/code&gt;. This user has an administrator access and can be used to create additional users and manage their access through roles.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
