<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Password Policy for all appliance users on</title><link>https://docs.protegrity.com/10.2/docs/aog/web_user_interface_management/aog_passwordpolicy_app_services/</link><description>Recent content in Password Policy for all appliance users on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/10.2/docs/aog/web_user_interface_management/aog_passwordpolicy_app_services/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing Roles</title><link>https://docs.protegrity.com/10.2/docs/aog/web_user_interface_management/aog_passwordpolicy_app_services/aog_managing_roles/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/web_user_interface_management/aog_passwordpolicy_app_services/aog_managing_roles/</guid><description>&lt;p>Roles are templates that include permissions and users can be assigned to one or more roles. Users in the appliance must be attached to a role.&lt;/p>
&lt;p>The default roles packaged with ESA are as follows:&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Roles&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;th>Permissions&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Policy Proxy User&lt;/td>
 &lt;td>Allows a user to connect to DSG via SOAP/REST and access web services using Application Protector (AP).&lt;/td>
 &lt;td>Proxy-User&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Policy User&lt;/td>
 &lt;td>Allows user to connect to DSG via SOAP/REST and perform security operations using Application Protector (AP).&lt;/td>
 &lt;td>Policy-User&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Security Administrator Viewer&lt;/td>
 &lt;td>Role that can view the ESA Web UI, CLI, and reports.&lt;/td>
 &lt;td>Security Viewer, Appliance CLI Viewer, Appliance web viewer, Reports Viewer&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Shell Accounts&lt;/td>
 &lt;td>Role who has direct SSH access to Appliance OS shell. &lt;/br>&lt;strong>Note&lt;/strong>: It is recommended that careful consideration is taken when assigning the Shell Accounts role and permission to a user. &lt;/br> Ensure that if a user is assigned to the Shell Account role, no other role is linked to the same user. The user has no access to the Web UI or CLI, except when the user has password policy enabled and is required to change password through Web UI.&lt;/td>
 &lt;td>Shell (non-CLI) Access&lt;/br>&lt;strong>Note&lt;/strong>: The user can access SSH directly if the permission is tied to this role.&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Security Administrator&lt;/td>
 &lt;td>Role who is responsible for setting up data security using ESA policy management, which includes but is not limited to creating policy, managing policy, and deploying policy.&lt;/td>
 &lt;td>Security Officer, Reports Manager, Appliance Web Manager, Appliance CLI Administrator, Export Certificates, DPS Admin, Directory Manager, Export Keys, RLP Manager&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>The capabilities of a role are defined by the permissions attached to the role. Though roles can be created, modified, or deleted from the appliance, permissions cannot be edited. The permissions that are available to map with a user and packaged with ESA as default permissions are as follows:&lt;/p></description></item><item><title>Configuring the proxy authentication settings</title><link>https://docs.protegrity.com/10.2/docs/aog/web_user_interface_management/aog_passwordpolicy_app_services/aog_configure_proxy_auth_settings/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/web_user_interface_management/aog_passwordpolicy_app_services/aog_configure_proxy_auth_settings/</guid><description>&lt;p>To configure the proxy authentication from the Web UI, the directory_administrator permission must be associated with the required role. It is also possible to do this through the CLI manager. For more information about configuring LDAP from the CLI manager, refer to &lt;a href="https://docs.protegrity.com/10.2/docs/aog/command_line_interface_cli_manager/working_with_administration/managing_ldap/aog_proxy_authentication/">here&lt;/a>.&lt;/p>
&lt;!-- If the number of unsuccessful password attempts exceed the defined value in the password policy, the account gets locked.

For more information about Password Policy, refer to [Password Policy for the LDAP Users](../concepts/aog_password_policy_for_all_appliance_services/#). -->
&lt;p>Perform the following steps to configure proxy authentication settings.&lt;/p></description></item><item><title>Working with External Groups</title><link>https://docs.protegrity.com/10.2/docs/aog/web_user_interface_management/aog_passwordpolicy_app_services/aog_external_groups/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/web_user_interface_management/aog_passwordpolicy_app_services/aog_external_groups/</guid><description>&lt;p>The directory service providers, such as, Active Directory (AD) or Oracle Directory Server Enterprise Edition (ODSEE), are identity management systems that contain information about the enterprise users. You can map the users in the directory service providers to the various roles defined in the Appliances. The External Groups feature enables you to associate users or groups to the roles.&lt;/p>
&lt;p>You can import users from a directory service to assign roles for performing various security and administrative operations in the appliances. Using External Groups, you connect to an external source, import the required users or groups, and assign the appliance-specific roles to them. The appliances automatically synchronize with the directory service provider at regular time intervals to update user information. If any user or group in a source directory service is updated, it is reflected across the users in the external groups. The updates made to the local LDAP do not affect the source directory service provider.&lt;/p></description></item></channel></rss>