CA PAM MySQL Target Connector

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

We are currently integrating PAM with MySQL databases, we using the KB guide to integrate with MySQL Target Connector - How to use the MySQL Target Connector

We found that our master account failed to manage /alter the other target account. Examples are below:

1. if the user/target account (user_test01) had multiple access to schema/database in MySQL our master account failed to alter the password of the target account (user_test01).

2. if the user/target account (user_test02) only had access to only one schema/database in MySQL our master account successfully managed/alter the password of the target account (user_test02)

It seems like PAM cannot manage MySQL target user if the user has multiple access/grantee to schema/database, but it works if it's only part of one schema/database.

Environment

Release : 4.1

Component : PRIVILEGED ACCESS MANAGEMENT

Cause

When you define the target account, you have to provide one specific database name, and that is a current design and the product is working as per design.

Resolution

If the ability to manage a single target account that is part of multiple schema/databases, please do file in a product enhancement request.