Managing Customized Database Resource Types and Resources11 minutes to read
PAM360 supports managing certain resource types by default and allows you to add new resource types as required. In addition to that, you can also create and configure new database resource types with a customized set of database attributes. Doing so will allow you to add the uniquely configured MS SQL Server, MySQL Server, PostgreSQL, Oracle DB Server, or Sybase ASE databases in your organization as the new resources in PAM360. With this, you will gain the flexibility to perform password resets, password verifications, account discovery, and SQL auto logon session processes for the uniquely configured databases, tailored to your specific needs, precisely empowering the organization to align database resources in PAM360 on a required basis. Notes: The attributes of the default database resource types cannot be edited. To manage your uniquely configured database via PAM360, follow these steps:
This document will help you learn various processes involved in creating and managing custom database resources via PAM360.
1. Roles Required - To Manage Customized Database ResourcesUsers with Privileged Administrator and Administrator roles can manage customized database resource types and can manage JDBC properties in PAM360 by default. To grant this responsibility to other users, you can create a custom role with Manage JDBC Properties, Configure Custom Database Connections, and Manage Custom Database Connections privileges enabled.
Users assigned with the above privileges can configure and manage customized database resource types and manage JDBC properties accordingly via PAM360. 2. Creating the JDBC PropertiesBy default, PAM360 provides several JDBC properties that supports connecting with the SQL server. To add new JDBC properties for your database resource type,
Note: Users can also open the JDBC Properties page when creating the database resource type by clicking View JDBC Properties. 3. Creating a Customized Database Resource TypeTo create a custom database resource type,
Note: Please exercise caution while validating all the configured values for the database connection. Misconfigured values may lead to SQL Injection and other security breaches. ![]() For example, if your desired SQL server is NoSQL server such as MongoDB, select an SQL server from the dropdown and proceed with the configuration: Note: The approval is required for adding or changing the custom database resource type attributes, not for editing or managing customized database resources at resource level in PAM360. Note: The resource type addition request can be approved by navigating to Admin >> Access Review >> DB Resource Configuration Request or directly from the notification list at the top pane of the user interface. ![]() 4. Editing the Customized Database Resource Type at Resource LevelTo edit the customized database resource that you have created via a new resource type, do the following steps:
![]() 5. Editing Customized Database Resource Types in BulkWhile creating a new customized database resource type, you can select any of the available default database resource types as the template. If you have created many new resource types with diverse existing database templates, you can also edit them in bulk at the resource level as required. To do so,
For example, you have established two new resource type categories, named AMP Database and KMP Database, each equipped with connection templates of MS SQL Server and PostgreSQL databases. Under each resource type category, three database resources have been added. Now, if you need to make bulk modifications to the connection properties of the three resources under the AMP Database resource type and the system properties of the three resources under the KMP Database resource type, follow these steps:
| |