Enterprise Administration Guide › Planning Your PUPM Implementation › Password Consumers › Implementation Considerations for Password Consumers

Implementation Considerations for Password Consumers

Before you implement password consumers, consider the following:

• To use software development kit, database, and Windows Run As password consumers, you must install CA Access Control on the PUPM endpoint with the PUPM Integration feature enabled.
• To use JDBC database password consumers, the application that connects to the database must use JRE 1.5 or later.
• To use OCI database password consumers, the application that connects to the database must use OCI8 or later.
• To use ODBC or OLEDB database password consumers with a non-default driver, you must contact CA Technologies Support.

  Note: The default drivers are defined in the ApplyOnProcess registry entry in the registry sub-key for the ODBC or OLEDB plug-in. For assistance, contact CA Support at http://ca.com/support.

• To use the Java PUPM SDK password consumer, the Java application that you write must use JRE 1.5 or later.
• To use the .NET PUPM SDK password consumer, you must install the .NET Framework 2.0 or later on the endpoint.
• When you discover service accounts to create a Windows Service or Windows Scheduled Task password consumer, CA Access Control discovers only services that are run by accounts for which you can change the password.
• To discover service accounts that are domain accounts, you must create a PUPM endpoint that represents the domain controller (DC) on which the accounts reside. The endpoint must have the following attributes:
  • Endpoint type—Windows Agentless
  • Is Active Directory—True
  • Host Domain—The domain name of which the DC is a member
  • User Domain—The domain name of which users defined on the DC are members

    Note: Specify the user domain only if the administrative account is from a different domain than the domain in which the accounts reside.

More information:

Discover Service Accounts

ODBCPlg

OLEDBPlg