https://docs.riaproducts.com/dih/4.x.x/docs/security/ Recent content in Security on RIA Docs Hugo en https://docs.riaproducts.com/dih/4.x.x/docs/security/authentication-and-authorization/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.riaproducts.com/dih/4.x.x/docs/security/authentication-and-authorization/ <h2 id="overview">Overview<a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"></a></h2> <p>DIH has its own security model to manage who can login and what a user can access.</p> <figure><img class="lightbox-trigger" src="https://docs-riaproducts.s3.us-east-1.amazonaws.com/dih-ga/images/userguidev3/security_model-diagram.png" alt=""><figcaption></figcaption></figure> <h2 id="boot-properties">Boot properties<a class="td-heading-self-link" href="#boot-properties" aria-label="Heading self-link"></a></h2> <p>Note that the authorization as described below is only in effect if the <code>ria-boot.properties</code> have been specified as shown in the purple block, bottom-left of the diagram.</p> <h2 id="user">User<a class="td-heading-self-link" href="#user" aria-label="Heading self-link"></a></h2> <p>The <code>UA_AUTH_USER</code> specifies a user id, full name and a password. The password is encrypted and used to authenticate a user at login. If federated SSO or LDAP is used for authentication, the password defined on this table is ignored because the authentication would be done by the SSO provider or LDAP store. The user definition is still required because all the authorization and audit tracking is associated with this user definition.</p>