Resolved Issues in 3.4
Lists the issues that are resolved in Release 3.4.
The following table lists the issues resolved in Release 3.4:
Internal Defect ID
The number of session logs in csv format was inconsistent.
Session recording fails for mainframe session requests for which protocol extensions are enabled in the client (by setting the BlueZone emulator Enable Extensions option).
SSH applet terminal characters are blurred on CA PAM Client on MacOS Mojave.
Radius authentication does not working properly when multiple Radius servers are configured with OTP and entered into PAM.
Credential Manager Administrators With the TargetAdmin Role Can Promote Their Own Privileges,
Not receiving emails for Forced Deactivation Alert.
CSV Import does not provide good failure logs.
Attempting to connect to the PAM server from the PAM client intermittently results in a "CA PAM Server is starting up. Please try again later." error.
Cannot export session logs after upgrade to CA PAM 3.3.
When integrating PAM 3.3 with PAMSC, the integration only works when login integration is disabled. When trying to use the login integration feature, the connection cannot be made.
Credential Management reports reading metric data start failing.
Not able to use backspace on AIX 7.2 target servers.
Verification of TACACS accounts fails after upgrading to 3.3.1.
Credential Manager database is deactivated on secondary and primary master instances causing users to see errors and be unable to check out passwords.
Wrong target account updated when two AD accounts with the same account name exist in a parent and child domain.
When using an A2A Client to retrieve large amounts of account passwords (in batches) password retrieval intermittently fails with 401 errors.
An unsuccessful verifyAccountPassword outputs two events in the syslog.
Large number of Session Recordings causing performance issues.
Conflict between NIM and PAM when ServiceNow integration is configured with Proxy.
Unable to synchronize AWS Key Pair accounts for GovCloud.
PAM is unable to connect to the AWS Management Console for GovCloud. An error related to DNS appears.
Passwords incorrectly showing as expired for many target accounts on PAM UI.
The value for groupReplicationGroupName is incorrect.
Unable to rotate AWS Key Pair credentials for GovCloud
20080883 and 20307909
Password View Request table on the Access page incorrectly refreshes every five seconds.
Customer cannot rotate password accounts in AzureGov environment.
PAM-PAMSC Integration Broken for LDAP PAM Users
Scheduled job for Azure target accounts is failing.
/api.php/v1/passwords/viewRequests.json fails on 3.3.2 when only the requestPeriodStart is provided
Script Filters in A2A Request Group are not honoured.
Cluster startup taking too long.
Problems if there was a cluster stop and then start again after recovering from a group replication outage.
API response mismatch when compared with 3.2.2.
Cluster fails to start if /var/tmp/fulldump.mbi file exists on the receiving node.
Replication to the primary site sometimes fails.
Unable to manage Tags and Groups via the REST API.
Password rotation does not work after upgrade to 3.3.2.
Auto archiving is not working after upgrading to version 3.3.2
Many "outside of valid range for type java.lang.Integer" exceptions in tomcat logs from AnsiSQLEventQueueDAO class.
Problem joining node to primary site after removing it and then patching it with 220.127.116.11
Privileges shown as 'available' and 'selected' at the same time.
Problems logging in to a mainframe running CA LDAP on RACF after upgrading from 3.2.2 to 3.3.2.
Cluster start results in a Restore of local database content failures